| 2 | Approval of Agenda | |
|---|---|---|
| R1-2102280 | Draft Agenda of RAN1#104bis-e meeting | RAN1 Chair |
| R1-2102283 | RAN1#104bis-e Meeting Invitation, Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
| R1-2102284 | Additional Guidelines for RAN1#104bis-e-Meeting Management | RAN1 Chair |
| R1-2102431 | Draft Agenda of RAN1#104bis-e meeting | RAN1 Chair |
| 3 | Highlights from RAN plenary | |
| R1-2102282 | Highlights from RAN#91-e | RAN1 Chair |
| 4 | Approval of Minutes from previous meetings | |
| R1-2102281 | Report of RAN1#104-e meeting | ETSI MCC |
| 5 | Incoming Liaison Statements | |
| R1-2102285 | LS Reply to RAN1 on CBRA based Beam Failure Recovery | RAN2, Apple |
| R1-2102286 | LS on uplink timing alignment for small data transmissions | RAN2, Lenovo |
| R1-2102287 | Reply LS on PUSCH skipping with UCI in Rel-16 | RAN2, vivo |
| R1-2102288 | Reply LS on AN-PDB and PER targets for satellite access | RAN2, Qualcomm |
| R1-2102289 | Reply LS on Rel-16 NR Positioning Correction | RAN2, Huawei |
| R1-2102290 | Reply LS on PC5 DRX operation | RAN2, LG Electronics |
| R1-2102291 | Reply LS on DAPS-like solution for service interruption reduction | RAN2, Ericsson |
| R1-2102292 | Reply on LS on DC location reporting for intra-band UL CA | RAN2, Apple |
| R1-2102293 | LS on gNB-based propagation delay compensation | RAN3, Nokia |
| R1-2102294 | LS on Granularity of the H/S/NA Slot Configurations for the IAB-DU | RAN3, Ericsson |
| R1-2102295 | Reply LS on Latency of NR Positioning Protocols | RAN3, Ericsson |
| R1-2102296 | LS on Rel-17 Tx switching enhancements | RAN4, China Telecom |
| R1-2102297 | Reply LS on Beam switching gaps for Multi-TRP UL transmission | RAN4, Samsung |
| R1-2102298 | Reply LS on PUCCH and PUSCH repetition | RAN4, Qualcomm |
| R1-2102299 | LS on timing of neighbor cell RSS-based measurements | RAN4, Qualcomm |
| R1-2102300 | Reply LS on temporary RS for efficient SCell activation in NR CA | RAN4, Huawei |
| R1-2102301 | LS on Signaling scheme of Transparent TxD | RAN4, vivo |
| R1-2102302 | LS on Rel-16 updated RAN4 UE features lists for LTE and NR | RAN4, CMCC |
| R1-2102303 | Further Reply LS on power control for NR-DC | RAN4, vivo |
| R1-2102304 | LS on Rel-16 updated RAN4 UE features lists for LTE and NR | RAN4, CMCC |
| R1-2102305 | LS on RSS based RSRQ for LTE-MTC | RAN4, Huawei |
| R1-2102306 | LS on Scheduling Location in Advance to reduce Latency | SA2, Qualcomm |
| R1-2102307 | Reply LS on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) | SA2, Qualcomm |
| R1-2102308 | Reply LS on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) | SA4, Qualcomm |
| R1-2102483 | [DRAFT] Reply LS on PUCCH and PUSCH repetition | ZTE |
| R1-2102485 | [DRAFT] Reply LS on power control for NR-DC | ZTE |
| R1-2102505 | Draft reply LS on PUCCH/PUSCH repetition and scenarios | OPPO |
| R1-2102554 | Reply LS on 3GPP NR Rel-16 URLLC and IIoT performance evaluation | RAN, Ericsson |
| R1-2102577 | Discussion on LS from RAN2 on SL DRX design | CATT, GOHIGH |
| R1-2102853 | Discussion on RAN4 LS on timing of neighbor cell RSS-based measurements | ZTE |
| R1-2102923 | Discussion on RAN4 LS on PUCCH and PUSCH repetition | vivo |
| R1-2102924 | Draft Reply LS on New Standardized 5QIs for 5G-AIS | vivo |
| R1-2102925 | Draft Reply LS on measuring CSI-RS during SCell activation | vivo |
| R1-2102926 | Draft Reply LS on Scheduling Location in Advance to reduce Latency | vivo |
| R1-2102927 | Draft Reply LS on Granularity of the H/S/NA Slot Configurations for the IAB-DU | vivo |
| R1-2102928 | Draft Reply LS on SL DRX design | vivo |
| R1-2102929 | Draft Reply LS on power control for NR-DC | vivo |
| R1-2102930 | Draft Reply LS on uplink timing alignment for small data transmissions | vivo |
| R1-2103065 | Discussion on timing of neighbor cell RSS-based measurements | Qualcomm Incorporated |
| R1-2103136 | Reply to RAN3 LS on Granularity of the H/S/NA Slot Configurations for the IAB-DU | Qualcomm Incorporated |
| R1-2103137 | [Draft] LS response on New Standardized 5QIs for 5G-AIS | Qualcomm Incorporated |
| R1-2103210 | Draft reply LS on Granularity of the H/S/NA Slot Configurations for the IAB-DU | Samsung |
| R1-2103282 | Discussion on the Reply LS on New Standardized 5QIs for 5G-AIS | ZTE, Sanechips |
| R1-2103283 | [draft]Reply LS on sidelink DRX | ZTE, Sanechips |
| R1-2103284 | About reply LS on Granularity of the HSNA Slot Configurations for the IAB-DU | ZTE, Sanechips |
| R1-2103285 | Discussion on simultaneous UL transmissions for DAPS-like solution in IAB | ZTE, Sanechips |
| R1-2103322 | Draft reply LS on Granularity of the H/S/NA Slot Configurations for the IAB-DU | ETRI |
| R1-2103323 | Draft reply LS on DAPS-like solution for service interruption reduction | ETRI |
| R1-2103388 | Discussion on LS on half-duplex operation | Huawei, HiSilicon |
| R1-2103624 | Draft reply LS on PUCCH and PUSCH repetition | LG Electronics |
| R1-2103628 | Draft reply LS on Granularity of the H/S/NA Slot Configurations for the IAB-DU | LG Electronics |
| R1-2103690 | [Draft] Reply on Scenarios for PUCCH and PUSCH Repetition | Ericsson |
| R1-2103717 | Consideration of SL DRX | ZTE, Sanechips |
| R1-2103718 | Draft reply LS on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) | OPPO |
| R1-2103749 | Discussion on reply LS on new standardized 5QIs for 5G-AIS | Huawei, HiSilicon |
| R1-2103752 | Discussion on RAN2 LS on DRX impact | Huawei, HiSilicon |
| R1-2103753 | Discussion on LS on IAB-DU H/S/NA Configuration per Cell | Huawei, HiSilicon |
| R1-2103756 | Discussion on scheduling location in advance to reduce latency | Huawei, HiSilicon |
| R1-2103757 | UL power control for NR-NR dual connectivity | Huawei, HiSilicon |
| R1-2103758 | Discussion on Reply LS on PUCCH and PUSCH repetition | Huawei, HiSilicon |
| R1-2103760 | Discussion on timing of neighbor cell RSS-based measurements | Huawei, HiSilicon |
| R1-2103769 | About reply LS on Granularity of the HSNA Slot Configurations for the IAB-DU | ZTE, Sanechips |
| R1-2103864 | RAN1#104b-e preparation phase on LSs | RAN1 Chair |
| R1-2104023 | LS on Status Update on XR Traffic | SA4, Qualcomm |
| R1-2104119 | Reply LS on PUCCH and PUSCH repetition | RAN1, Qualcomm |
| 5.1 | RAN1 Aspects for RF requirements for NR frequency range 1 (FR1) | |
| R1-2102365 | Discussion on Rel-17 Tx switching enhancement | OPPO |
| R1-2102484 | Discussion on Rel-17 UL Tx Switching | ZTE |
| R1-2102583 | Discussion on R17 enhancements for UL TX switching | CATT |
| R1-2102860 | Discussion on Rel-17 uplink Tx switching | China Telecom |
| R1-2102876 | Discussion on Rel-17 UL Tx Switching | CMCC |
| R1-2102931 | Discussion on Rel-17 Tx switching enhancements | vivo |
| R1-2103138 | Discussion on R17 UL Tx switching | Qualcomm Incorporated |
| R1-2103387 | Discussions on enhancements for UL Tx switching | Huawei, HiSilicon |
| R1-2103782 | Summary of Rel-17 uplink Tx switching | Moderator (China Telecom) |
| R1-2104137 | Reply LS on Rel-17 uplink Tx switching | RAN1, China Telecom |
| 5.2 | RAN1 Aspects for NR small data transmissions in INACTIVE state | |
| R1-2102312 | RA and CG based small data transmission | Huawei, HiSilicon |
| R1-2102578 | Discussion on remaining issues on small data transmission | CATT |
| R1-2102647 | On physical layer aspects of small data transmission | Nokia, Nokia Shanghai Bell |
| R1-2102817 | Discussion on RAN1 aspects for NR small data transmissions in INACTIVE state | Ericsson |
| R1-2102837 | Discussion on NR small data transmissions in INACTIVE state | OPPO |
| R1-2102932 | Discussion on RAN1 impacts for small data transmisison | vivo |
| R1-2103013 | Discussion on physical layer aspects of small data transmission | Intel Corporation |
| R1-2103075 | Discussion on physical layer aspects of small data transmission | Apple |
| R1-2103139 | UL timing alignment for SDT | Qualcomm Incorporated |
| R1-2103211 | Discussion on TA validity check based on RSRP threhold | Samsung |
| R1-2103286 | Configuration of CORESET and search space for SDT | Sony |
| R1-2103334 | Discussion on physical layer aspects of small data transmission | LG Electronics |
| R1-2103380 | Physical layer aspects of small data transmission | InterDigital, Inc. |
| R1-2103494 | Discussion on the physical layer aspects of small data transmission | ZTE, Sanechips |
| R1-2103678 | Discussion on RAN1 aspects for NR small data transmissions in INACTIVE state | Ericsson |
| R1-2103925 | Summary of the physical layer aspects of small data transmission | Moderator (ZTE) |
| R1-2103926 | Draft LS on the association between SSBs and CG resources for CG-SDT | Moderator (ZTE) |
| R1-2103994 | Reply LS on uplink timing alignment for small data transmissions | RAN1, Lenovo |
| R1-2103995 | Summary of reply LS on UL TA for SD ([104b-e-NR-R17-SDT-LS-01] NWM discussion) | Moderator (Lenovo) |
| R1-2104012 | Reply LS on uplink timing alignment for small data transmissions | RAN1, Lenovo |
| 6.1 | Maintenance of E-UTRA Releases 8 – 15 | |
| R1-2102846 | Correction on MPDCCH assignment procedure | ZTE |
| R1-2102847 | Correction on PDSCH dropping for multicast in special subframe | ZTE |
| R1-2102851 | Discussion on NPUSCH postponement when overlapping with NPRACH resource | ZTE |
| R1-2102852 | Clarification on NPUSCH postponement for NB-IoT | ZTE |
| R1-2103066 | Correction for DCI size alignment in NBIOT | Qualcomm Incorporated |
| R1-2103729 | Clarification on the UE transmit power for the 2-of-3 subcarrier allocation in sub-PRB | Ericsson |
| R1-2103730 | Clarification on the UE transmit power for the 2-of-3 subcarrier allocation in sub-PRB | Ericsson |
| R1-2103807 | RAN1#104b-e preparation phase on Maintenance of E-UTRA Releases 8-15 | Ad-Hoc Chair (Ericsson) |
| R1-2103873 | Moderator Summary [104b-e-LTE-6.1CRs-04] | Moderator (Ericsson) |
| R1-2103909 | Correction for DCI size alignment in NBIOT | Qualcomm Incorporated |
| R1-2103910 | Correction for DCI size alignment in NBIOT | Qualcomm Incorporated |
| R1-2103917 | Correction on MPDCCH assignment procedure | ZTE |
| R1-2103918 | Correction on MPDCCH assignment procedure | ZTE |
| R1-2103919 | Correction on MPDCCH assignment procedure | ZTE |
| R1-2103920 | Correction on PDSCH dropping for multicast in special subframe | ZTE |
| R1-2103921 | Correction on PDSCH dropping for multicast in special subframe | ZTE |
| R1-2103922 | Correction on PDSCH dropping for multicast in special subframe | ZTE |
| R1-2103952 | Summary of [104b-e-LTE-6.1CRs-02] email discussion/approval on R1-2102851 and R1-2102852 | Moderator (ZTE) |
| R1-2103970 | Session notes for 6.1 (Maintenance of E-UTRA Releases 8-15) | Ad-Hoc Chair (Ericsson) |
| R1-2104017 | FL summary for the email thread [104b-e-LTE-6.1CRs-01] | Moderator (ZTE) |
| 6.2 | Maintenance of E-UTRA Release 16 | |
| R1-2103971 | Session notes for 6.2.1 (Maintenance of Additional MTC Enhancements) and 6.2.2 (Maintenance of Additional Enhancements for NB-IoT) | Ad-hoc Chair (Samsung) |
| 6.2.1 | Maintenance of Additional MTC Enhancements | |
| R1-2102848 | Correction on PUCCH transmit power control for LTE-M | ZTE |
| R1-2102849 | Correction on bundling parameter for multi-TB scheduling for LTE-M | ZTE |
| R1-2103714 | Timing of RSS in neighbor cells for Rel-16 LTE-MTC | Ericsson |
| R1-2103721 | PUR maintenance issues for Rel-16 LTE-MTC | Ericsson |
| R1-2103822 | FL summary for Multi-TB and PUR issues for Rel-16 LTE-MTC | Moderator (Ericsson) |
| R1-2103963 | Clarification of PUSCH PRB resources for PUR in LTE-MTC | Moderator (Ericsson), Ericsson |
| R1-2104032 | [104b-e-LTE-eMTC5-01] Reply LS on timing of neighbor cell RSS-based measurements | Moderator (Qualcomm Incorporated) |
| R1-2104033 | Reply LS on timing of neighbour cell RSS-based measurements | RAN1, Qualcomm Incorporated |
| R1-2104034 | Correction on bundling parameter for multi-TB scheduling for LTE-M | Moderator (Ericsson), ZTE, Sanechips, Ericsson |
| R1-2104035 | Correction on PUCCH transmit power control for LTE-M | Moderator (Ericsson), ZTE, Sanechips, Ericsson |
| 6.2.2 | Maintenance of Additional Enhancements for NB-IoT | |
| R1-2102850 | Correction on multi-TB gap for multicast in NB-IoT | ZTE |
| R1-2103722 | PUR maintenance issues for Rel-16 NB-IoT | Ericsson |
| R1-2103762 | Correction on multi-TB scheduling for NB-IoT | Huawei, HiSilicon |
| R1-2103998 | Correction on multi-TB scheduling for NB-IoT | Moderator (Huawei), ZTE, Sanechips, Huawei, HiSilicon |
| R1-2104015 | Feature summary on 104b-e-LTE-NB_IoTenh3-01 | Moderator (Huawei) |
| R1-2104016 | Correction on subcarrier indication for PUR | Moderator (Huawei), Ericsson, ZTE, Sanechips, Huawei, HiSilicon |
| 6.2.3 | Maintenance of DL MIMO efficiency enhancements for LTE | |
| R1-2103761 | Correction on additional SRS symbols | Huawei, HiSilicon |
| R1-2103934 | Correction on additional SRS symbols | Huawei, HiSilicon |
| R1-2103972 | Session notes for 6.2.3 (Maintenance of DL MIMO efficiency enhancements for LTE) | Ad-Hoc Chair (Samsung) |
| R1-2104014 | Feature summary on 104b-e-LTE-LTE_DL_MIMO_EE-01 | Moderator (Huawei) |
| 7.1 | Maintenance of Release 15 NR | |
| R1-2102366 | Discussion on PUSCH skipping with UCI overlapping | OPPO |
| R1-2102427 | Draft CR on PUCCH close loop power control | OPPO |
| R1-2102428 | Draft CR on PUCCH repetition | OPPO |
| R1-2102429 | Draft CR on interaction between SFI and data repetition | OPPO |
| R1-2102430 | Draft CR on PUCCH power control | OPPO |
| R1-2102440 | Discussion on UL skipping for CG PUSCH | Spreadtrum Communications |
| R1-2102480 | Discussion on UL skipping for PUSCH | ZTE |
| R1-2102481 | Correction on UL DAI for Type-2 HARQ-ACK codebook | ZTE |
| R1-2102482 | Correction on UL DAI for Type-2 HARQ-ACK codebook | ZTE |
| R1-2102579 | Correction on common PUCCH resource in initial UL BWP | CATT |
| R1-2102580 | Correction on overlapping between positive SR and PUSCH without UL-SCH | CATT |
| R1-2102581 | Corrections to TS 38.213 | CATT |
| R1-2102582 | Discussion on PUSCH skipping | CATT |
| R1-2102584 | Correction to UE CSI computation time | CATT |
| R1-2102693 | Clarification on back-to-back PUSCHs scheduling restriction in Rel-15 | MediaTek Inc. |
| R1-2102796 | Clarification on DAI size in DCI format 1_1 for CA | MediaTek Inc. |
| R1-2102816 | Remaining issues with PUSCH skipping (without LCH and PHY prioritization) (Rel-16) | Nokia, Nokia Shanghai Bell |
| R1-2102933 | Discussion on UE behavior when DCI format 2_0 is not monitored outside DRX active time | vivo |
| R1-2102934 | Discussion on PUSCH skipping with overlapping UCI on PUCCH in Rel-16 | vivo |
| R1-2102935 | Discussion on collision handling for PRACH transmission | vivo |
| R1-2102936 | Disucssion on CSI-RS Resource counting for UE feature 2-24 and 2-33 | vivo |
| R1-2102937 | Disucssion on CSI request constraint per slot considering xCC scheduling with different numerology | vivo |
| R1-2102953 | Draft CR on PDSCH default TCI state | ZTE |
| R1-2103076 | Discussion on UE capability for L1-RSRP measurement | Apple |
| R1-2103077 | Correction for HARQ-ACK timing in Rel-15 and Rel-16 | Apple, Ericsson |
| R1-2103078 | Discussions on PUSCH skipping in Rel-16 | Apple |
| R1-2103079 | Discussions on PUSCH UCI Multiplexing without HARQ-ACK PUCCH in Rel-15 | Apple |
| R1-2103140 | Clarification in the Wideband PRG computation | Qualcomm Incorporated |
| R1-2103141 | Timelines for SRS carrier switching | Qualcomm Incorporated |
| R1-2103199 | Discussion on PUSCH with ULSkipping and repetition | Ericsson |
| R1-2103384 | Discussion on PUSCH transmission power control corresponding to RAR UL grant | Huawei, HiSilicon |
| R1-2103385 | Clarification on cross-carrier operation with different SCS | Huawei, HiSilicon |
| R1-2103386 | Discussion on UL skipping | Huawei, HiSilicon |
| R1-2103465 | Correction on condition for monitoring occasions for Type0/0A/2-PDCCH CSS set | Sharp |
| R1-2103503 | Draft CR on prioritization between SRS and PUCCH | LG Electronics |
| R1-2103553 | Discussion on UL skipping for PUSCH repetition | NTT DOCOMO, INC. |
| R1-2103677 | Draft CR on PUSCH skipping with repetition (Rel-16) | Nokia, Nokia Shanghai Bell |
| R1-2103742 | Correction on PUSCH transmission power control corresponding to RAR UL grant in Rel-15 | Huawei, HiSilicon |
| R1-2103743 | Correction on PUSCH frequency hopping in 38.214 | Huawei, HiSilicon |
| R1-2103744 | Correction on out-of-order HARQ operation in 38.214 | Huawei, HiSilicon |
| R1-2103755 | Correction on PDCCH blind detection capability for CA in TS38.213 | Huawei, HiSilicon |
| R1-2103759 | Correction on prioritization rules of SRS carrier switching | Huawei, HiSilicon |
| R1-2103770 | Clarification on cross-carrier operation with different SCS | Huawei, HiSilicon |
| R1-2103779 | RAN1#104bis-e preparation phase initial summary on NR Rel-15 CRs | Ad-hoc chair (Samsung) |
| R1-2103780 | RAN1#104bis-e preparation phase final summary on NR Rel-15 CRs | Ad-hoc chair (Samsung) |
| R1-2103809 | Summary for [104b-e-NR-7.1CRs-03] Discussion on collision handling for PRACH transmission | Moderator (vivo) |
| R1-2103891 | Summary on [104b-e-NR-7.1CRs-10] | Moderator (Samsung) |
| R1-2103904 | Summary on [104b-e-NR-7.1CRs-09] | Moderator (ZTE) |
| R1-2103913 | Editorial changes on [104b-e-NR-7.1CRs-09] | Moderator (ZTE) |
| R1-2103973 | Session notes for 7.1 (Maintenance of Release 15 NR) | Ad-hoc Chair (Samsung) |
| R1-2103997 | Correction on out-of-order HARQ operation in 38.214 | Moderator (Huawei), HiSilicon |
| R1-2103999 | Summary of [104b-e-NR-7.1CRs-07]: Correction on out-of-order HARQ operation in 38.214 | Moderator (Huawei) |
| R1-2104007 | 38.212 CR on DAI size determination for DCI format 1_1 in CA | Moderator (MediaTek), CATT |
| R1-2104008 | 38.212 CR on DAI size determination for DCI format 1_1/1-2 in CA | Moderator (MediaTek), CATT |
| R1-2104009 | Summary for [104b-e-NR-7.1CRs-01] Clarification on DAI Size in DCI Format 1_1 for CA | Moderator (MediaTek) |
| R1-2104043 | Timelines for SRS carrier switching | Moderator (Qualcomm Incorporated), Qualcomm Incorporated, ZTE |
| R1-2104067 | Summary of [104b-e-NR-7.1CRs-02] Correction on prioritization rules of SRS carrier switching | Moderator (Huawei) |
| R1-2104073 | Summary of [104b-e-NR-7.1CRs-05] discussion on PUSCH skipping with UCI overlapping (Rel16) | Moderator (vivo) |
| R1-2104105 | Summary of email discussion [104b-e-NR-7.1CRs-04] on the correction for HARQ-ACK timing | Moderator (Apple Inc.) |
| R1-2104112 | Rel-15 editorial corrections for TS 38.213 | Samsung |
| R1-2104113 | Rel-15 editorial corrections for TS 38.213 (mirrored to Rel-16) | Samsung |
| R1-2104129 | Rel-15 editorial corrections for TS 38.214 | Nokia |
| R1-2104130 | Rel-15 editorial corrections for TS 38.214 (mirrored to Rel-16) | Nokia |
| R1-2104140 | Summary on 104b-e-NR-7.1CRs-08 | Moderator (Apple Inc.) |
| 7.2 | Maintenance of Release 16 NR | |
| R1-2103657 | Alignment of notation | Ericsson |
| R1-2104114 | Rel-16 editorial corrections for TS 38.213 | Samsung |
| R1-2104123 | Alignment of notation | Ericsson |
| R1-2104131 | Rel-16 editorial corrections for TS 38.214 | Nokia |
| R1-2104139 | Alignment CR for TS 38.212 | Huawei |
| 7.2.1 | Maintenance of Two step RACH for NR | |
| R1-2102818 | Discussion on corrections for 2-step RACH | Ericsson |
| R1-2103403 | Correction on the configuration of RACH-related power control parameters | Huawei, HiSilicon |
| R1-2103495 | Editorial corrections on the DMRS description for MsgA | ZTE, Sanechips |
| R1-2103496 | FL summary on the maintenance of 2-step RACH | Moderator (ZTE) |
| R1-2103680 | Discussion on corrections for 2-step RACH | Ericsson |
| R1-2103924 | Summary of email discussion for [104-e-NR-2Step-RACH-01] | Moderator (ZTE) |
| 7.2.2 | Maintenance of NR-based Access to Unlicensed Spectrum | |
| R1-2102325 | Maintenance on channel access and HARQ procedures for NR Unlicensed | Huawei, HiSilicon |
| R1-2102326 | Maintenance on DL signals and channels for NR Unlicensed | Huawei, HiSilicon |
| R1-2102367 | Discussion on the remaining issues of HARQ enhancements | OPPO |
| R1-2102556 | Discussion on the remaining issues of initial access | OPPO |
| R1-2102587 | Correction on multiplexing timeline definition for Type-3 HARQ-ACK codebook | CATT,Huawei,HiSilicon, OPPO |
| R1-2102786 | Corrections related to DL Signals and Channels | Ericsson |
| R1-2102787 | Discussion on LS from RAN4 on measuring CSI-RS during SCell activation | Ericsson |
| R1-2102938 | Correction on 38.213 for SR reporting due to consistent LBT failure recovery | vivo |
| R1-2102939 | Maintenance for frequency hopping for NR-U configured grant | vivo |
| R1-2103142 | Invalid SSB in FBE | Qualcomm Incorporated |
| R1-2103212 | Correction on the conditions for DL channel access procedure | Samsung |
| R1-2103335 | Remaining issues of DL signals and channels and channel access procedure for NR-U | LG Electronics |
| R1-2103336 | Remaining issues of UL channels and HARQ procedure for NR-U | LG Electronics |
| R1-2103485 | Discussion on measuring CSI-RS during SCell activation | ZTE, Sanechips |
| R1-2103486 | Correction on MsgA PUSCH validation for FBE | ZTE, Sanechips |
| R1-2103554 | Maintenance for DL channel access mechanism | NTT DOCOMO, INC., Ericsson |
| R1-2103688 | Feature lead summary for NR-U DL Signals and Channels | Moderator (Lenovo) |
| R1-2103732 | Discussion on DL COT Detection in Semi-static Channel Access | Nokia, Nokia Shanghai Bell |
| R1-2103733 | Discussion on RAN4 LS on measuring CSI-RS during SCell activation | Nokia, Nokia Shanghai Bell |
| R1-2103777 | Feature lead summary on for initial access procedures enhancements | Moderator (Charter Communications) |
| R1-2103783 | Feature lead summary for Maintenance of UL Signals and Channels | Moderator (Ericsson) |
| R1-2103789 | FL summary for initial access signals and channels for NR-U CR | Moderator (Qualcomm) |
| R1-2103790 | Preparation phase email discussion summary for Rel.16 NR-U CR | Moderator (Qualcomm) |
| R1-2103894 | Correction on multiplexing timeline definition for Type-3 HARQ-ACK codebook | CATT, Huawei, HiSilicon, OPPO |
| R1-2103895 | Feature lead summary#1 on NR-U HARQ maintenance | Moderator (Huawei) |
| R1-2103896 | Correction on Type-3 HARQ-ACK codebook size ambiguity | Moderator (Huawei) |
| R1-2103931 | Feature lead summary for [104b-e-NR-NRU-01] Email discussion/approval on DL signals and channels | Moderator (Lenovo) |
| R1-2103932 | Feature lead summary for [104b-e-NR-NRU-05] Email discussion/approval on DL signals and channels | Moderator (Lenovo) |
| R1-2103974 | Session notes for 7.2.2 (Maintenance of NR-based Access to Unlicensed Spectrum) | Ad-Hoc Chair (Ericsson) |
| R1-2104030 | Correction on MsgA PUSCH validation for semistatic channel access | Moderator (Charter Communications), ZTE, Sanechips |
| R1-2104055 | Draft LS on maximum size change of switchTriggerToAddModList-r16 and switchTriggerToReleaseList-r16, and update to TS 38.300 | Moderator (Lenovo) |
| R1-2104056 | Draft CR: Correction on averaging CSI-RS for measuring CSI across DL bursts | Moderator (Lenovo) |
| R1-2104069 | Correction on the conditions for DL channel access procedure | Moderator (Nokia), Samsung, NTT DOCOMO, Ericsson |
| R1-2104070 | Clarifying the conditions for indicating Type 2 LBT for wideband scheduled PUSCH | Moderator (Nokia), Huawei, HiSilicon |
| R1-2104071 | Correction on SR reporting due to consistent LBT failure recovery | Moderator (Nokia), vivo |
| R1-2104072 | Feature Lead Summary on Channel Access Procedures for NR-U | Moderator (Nokia) |
| R1-2104094 | LS on maximum size change of switchTriggerToAddModList-r16 and switchTriggerToReleaseList-r16, and update to TS 38.300 | RAN1, Lenovo |
| R1-2104095 | Correction on averaging CSI-RS for measuring CSI across DL bursts | Moderator (Lenovo), LG Electronics |
| R1-2104096 | Draft LS on measuring CSI-RS during SCell activation | Moderator (Lenovo) |
| 7.2.3 | Maintenance of Integrated Access and Backhaul for NR | |
| R1-2102588 | Correction on search space definition for Type-3 CSS and USS | CATT |
| R1-2103498 | Clarification on availability indication for IAB-DU cell | ZTE, Sanechips |
| R1-2103713 | H/S/NA configuration per pair of IAB-DU cell and IAB-MT’s serving cell | Ericsson, AT&T |
| R1-2103797 | H/S/NA configuration per pair of IAB-DU cell and IAB-MT’s serving cell | Ericsson, AT&T |
| R1-2103993 | Session notes for 7.2.3 (Maintenance of Integrated Access and Backhaul for NR) | Ad-hoc Chair (Samsung) |
| R1-2104058 | Reply LS on Granularity of the H/S/NA Slot Configurations for the IAB-DU | RAN1, Ericsson |
| R1-2104059 | Conditions for IAB-DU soft resource availability | Moderator (AT&T), Qualcomm, Ericsson |
| 7.2.4 | Maintenance for 5G V2X with NR sidelink | |
| R1-2102368 | Remaining open issues and corrections for mode 1 RA | OPPO |
| R1-2102369 | Remaining open issues and corrections for mode 2 RA | OPPO |
| R1-2102589 | Discussion and TPs on resource allocation in NR V2X | CATT, GOHIGH |
| R1-2102590 | Discussion and TPs on Tie-break issues for PSFCH Tx and PSFCH Rx | CATT, GOHIGH |
| R1-2102591 | Discussion on timing offset between eNB and gNB in NR V2X | CATT, GOHIGH |
| R1-2102710 | A remaining issue on Mode-1 resource allocation for NR sidelink | Fujitsu |
| R1-2102711 | Remaining issues on physical layer procedures for NR sidelink | Fujitsu |
| R1-2102795 | Remaining open issues and corrections for procedure | OPPO |
| R1-2102940 | Maintenance on NR sidelink mode-1 resource allocation mechanism | vivo |
| R1-2102941 | Maintenance on NR sidelink mode-2 resource allocation mechanism | vivo |
| R1-2102942 | Maintenance on NR sidelink synchronization and procedure | vivo |
| R1-2103080 | On Remaining Issue of Sidelink Physical Layer Procedures | Apple |
| R1-2103081 | On Remaining Issues of Mode 2 Resource Allocation | Apple |
| R1-2103143 | Remaining Issues in Mode 2 Resource Allocation | Qualcomm Incorporated |
| R1-2103213 | Discussion on Issues for NR Sidelink Physical Layer Structure | Samsung |
| R1-2103375 | Discussion on essential corrections in physical layer structure | LG Electronics |
| R1-2103376 | Discussion on essential corrections in resource allocation procedure | LG Electronics |
| R1-2103377 | Discussion on essential corrections in physical layer procedure | LG Electronics |
| R1-2103391 | Remaining issues for sidelink physical layer procedure | Huawei, HiSilicon |
| R1-2103466 | Remaining issues on physical layer structure for NR sidelink | Sharp |
| R1-2103467 | Remaining issues on resource allocation for NR sidelink | Sharp |
| R1-2103468 | Remaining issues on synchronization mechanism and QoS management for NR sidelink | Sharp |
| R1-2103499 | Remaining issues on mode 1 | ZTE, Sanechips |
| R1-2103500 | SL PHY procedure on prioritization | ZTE, Sanechips |
| R1-2103501 | Draft CR of TS38.214 | ZTE, Sanechips |
| R1-2103516 | Remaining issues on resource allocation mode 2 | NEC |
| R1-2103555 | Maintenance for resource allocation mechanism mode 1 | NTT DOCOMO, INC. |
| R1-2103556 | Maintenance for sidelink physical layer procedure | NTT DOCOMO, INC. |
| R1-2103638 | Remaining issues on DL pathloss for sidelink power control | ASUSTeK |
| R1-2103639 | Remaining issues on sidelink mode 2 | ASUSTeK |
| R1-2103672 | Remaining issues on resource allocation mode-1 and sidelink procedure | ASUSTeK |
| R1-2103707 | Draft_CR_TS38.213 | Ericsson |
| R1-2103708 | Draft_CR_TS38.214 | Ericsson |
| R1-2103709 | Correction to PSCCH reserved bits definition | Ericsson |
| R1-2103750 | Correction on resource exclusion for other TBs | Huawei, HiSilicon |
| R1-2103751 | Correction on step 5 of mode 2 resource allcoation | Huawei, HiSilicon |
| R1-2103764 | Maintenance for Resource allocation for sidelink - Mode 1 | Nokia, Nokia Shanghai Bell |
| R1-2103765 | Maintenance for Resource allocation for sidelink - Mode 2 | Nokia, Nokia Shanghai Bell |
| R1-2103766 | Correction to PSFCH reception procedure for NACK-only case to mitigate half-duplex issue | Intel Corporation |
| R1-2103788 | Feature lead summary for physical layer procedure aspects in AI 7.2.4 | Moderator (LG Electronics) |
| R1-2103795 | Summary#1 for Rel-16 5G_V2X_NRSL QoS management and congestion control for sidelink | Moderator (Nokia) |
| R1-2103798 | Feature lead summary on Mode-2 resource allocation maintenance issues in Rel.16 5G V2X | Moderator (Intel Corporation) |
| R1-2103841 | Feature lead summary#1 on Resource allocation for NR sidelink Mode 1 | Moderator (Ericsson) |
| R1-2103842 | Feature lead summary#2 on Resource allocation for NR sidelink Mode 1 | Moderator (Ericsson) |
| R1-2103881 | Summary#1 for Rel-16 5G_V2X_NRSL QoS management and congestion control for sidelink | Moderator (Nokia) |
| R1-2103946 | Feature lead summary for email discussion/approval [104b-e-NR-5G_V2X-01] | Moderator (LG Electronics) |
| R1-2103947 | Feature lead summary for email discussion/approval [104b-e-NR-5G_V2X-04] | Moderator (LG Electronics) |
| R1-2103948 | Corrections for the reference signal used for sidelink power control | Moderator (LG Electronics) |
| R1-2103949 | Corrections for the multiplexing SL HARQ-ACK information on a PUSCH | Moderator (LG Electronics) |
| R1-2103959 | Feature lead summary#1 for Physical layer structure for sidelink | Moderator (Samsung) |
| R1-2104050 | [Draft] Correction of search space configuration for DCI formats 3_0 and 3_1 | Moderator (Ericsson), vivo, Nokia, Nokia Shanghai Bell |
| R1-2104051 | [Draft] LS on the configuration of search spaces for scheduling SL transmissions | Ericsson |
| R1-2104062 | Correction of search space configuration for DCI formats 3_0 and 3_1 | Moderator (Ericsson), vivo, Nokia, Nokia Shanghai Bell |
| R1-2104063 | LS on the configuration of search spaces for scheduling SL transmissions | RAN1, Ericsson |
| R1-2104084 | Outcome and TPs for discussion [104b-e-NR-5G_V2X-03] | Moderator (Intel Corporation) |
| R1-2104085 | Correction to sidelink resource identification procedure avoiding infinite loop issue | Moderator (Intel Corporation), OPPO, FUTUREWEI, Ericsson, Huawei, HiSilicon, CATT, GOHIGH, Nokia, Nokia Shanghai Bell, vivo |
| 7.2.5 | Maintenance of Physical Layer Enhancements for NR URLLC | |
| R1-2102349 | Remaining issues on SPS enhancements | Huawei, HiSilicon, SIA |
| R1-2102350 | On LCH prioritization and UL skipping | Huawei, HiSilicon |
| R1-2102370 | Discussion on PHY behaviour for collision between CG and DG with UCI overlapping | OPPO |
| R1-2102371 | Remaining issues on scheduling and HARQ | OPPO |
| R1-2102372 | Maintenance on UCI enhancements | OPPO |
| R1-2102486 | Discussion on the maximum number of configurable candidates for DCI format 2_4 | ZTE |
| R1-2102487 | Remaining issues on intra-UE multiplexing in Rel-16 URLLC | ZTE |
| R1-2102488 | Corrections on issues related to DMRS configuration for DCI format 1_2 | ZTE |
| R1-2102592 | Discussion on overlapping between CG PUSCH and DG PUSCH | CATT |
| R1-2102593 | Remaining issues on scheduling and HARQ enhancements | CATT |
| R1-2102594 | Remaining issues on UCI enhancements | CATT |
| R1-2102741 | Intra-UE Multiplexing and Prioritization for Rel-16 URLLC | Ericsson |
| R1-2102742 | Maintenance of PDCCH for Rel-16 NR URLLC | Ericsson |
| R1-2102743 | Miscellaneous Issues for Rel-16 NR URLLC | Ericsson |
| R1-2102822 | Maintenance of Rel-16 URLLC UCI enhancements | Nokia, Nokia Shanghai Bell |
| R1-2102823 | Maintenance of Rel-16 URLLC SPS enhancements | Nokia, Nokia Shanghai Bell |
| R1-2102824 | PHY priority handling for Msg 3 / Msg A and PHR / power scaling for UL skipping & UL CI | Nokia, Nokia Shanghai Bell |
| R1-2102943 | Maintenance on UCI enhancements | vivo |
| R1-2102944 | Corrections on parameter of MCS table set to qam256 | vivo |
| R1-2102945 | Maintenance on SPS enhancements | vivo |
| R1-2103082 | Correction to VRB-to-PRB in DCI Format 1_2 | Apple |
| R1-2103083 | UCI multiplexing and PUSCH skipping design in URLLC | Apple |
| R1-2103144 | Remaining issues on eCG enhancements for URLLC | Qualcomm Incorporated |
| R1-2103214 | Discussion on PUSCH skipping for URLLC | Samsung |
| R1-2103215 | Maintanence on PDCCH as PDSCH SLIV reference | Samsung |
| R1-2103216 | Maintanence on SPS PDSCH | Samsung |
| R1-2103270 | Remaining issues on UCI enhancements for eURLLC | Apple Europe Limited |
| R1-2103337 | PHR issues related to URLLC/IIOT WI | LG Electronics |
| R1-2103338 | Remaining issues of other aspects for URLLC/IIOT | LG Electronics |
| R1-2103397 | Discussion on new SLIV reference for Type 1 HARQ codebook | Huawei, HiSilicon |
| R1-2103428 | Correction to UE processing times for intra-UE prioritization | Intel Corporation |
| R1-2103469 | Remaining issue on channel inference for PUSCH with repetition Type B for NR URLLC | Sharp |
| R1-2103557 | Corrections on UCI enhancement for Rel-16 URLLC | NTT DOCOMO, INC. |
| R1-2103558 | Correction on PUSCH enhancements for Rel-16 URLLC | NTT DOCOMO, INC. |
| R1-2103773 | Preparation phase email discussion for Rel-16 eURLLC | Moderator (Huawei) |
| R1-2103774 | Feature lead summary on PDCCH enhancements | Moderator (Huawei) |
| R1-2103778 | Feature lead summary on PUSCH enhancements for NR eURLLC in AI 7.2.5 | Moderator (Apple Inc.) |
| R1-2103810 | Summary of the Remaining Issues on intra-UE prioritization/multiplexing and eCG | Moderator (vivo) |
| R1-2103835 | Feature lead summary on other aspects for URLLC and IIoT | Moderator (LG Electronics) |
| R1-2103836 | Summary #1 of [104b-e-NR-L1enh-URLLC-05] on other aspects for URLLC and IIoT | Moderator (LG Electronics) |
| R1-2103840 | Summary of the preparation phase: Remaining issues on HARQ and scheduling enhancements for URLLC | Moderator (Qualcomm) |
| R1-2103856 | Summary#1 on UCI enhancements for R16 URLLC | Moderator (OPPO) |
| R1-2103867 | Summary#1 of email thread [104b-e-NR-L1enh-URLLC-02] | Moderator (OPPO) |
| R1-2103975 | Session notes for 7.2.5 (Maintenance of Physical Layer Enhancements for NR URLLC/IIoT) | Ad-hoc Chair (Samsung) |
| R1-2104074 | Summary of [104b-e-NR-L1enh-URLLC-04] Email discussion/approval on remaining issues on Scheduling & HARQ enhancements | Moderator (Qualcomm) |
| R1-2104075 | Correction on Prioritization Timeline | Moderator (Qualcomm) |
| R1-2104077 | CR on the configuration for one PUCCH-Config with subslotLengthForPUCCH-r16 | Moderator (OPPO), CATT, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
| R1-2104078 | CR on not supporting Type 1 HARQ-ACK codebook for sub-slot HARQ-ACK in R16 | Moderator (OPPO), CATT, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
| R1-2104079 | CR on Number of PUCCH resource sets per PUCCH-config | Moderator (OPPO), NTT DOCOMO, Nokia, Nokia Shanghai Bell |
| R1-2104106 | Summary of [104b-e-NR-L1enh-URLLC-03] on PUSCH enhancements for NR eURLLC in AI 7.2.5 | Moderator (Apple Inc.) |
| R1-2104107 | Correction on UL cancellation due to dynamic SFI | Moderator (Apple Inc.), CATT |
| R1-2104108 | Correction on antenna port assumption for PUSCH repetition Type B | Moderator (Apple Inc.), Sharp |
| R1-2104125 | Summary #2 of [104b-e-NR-L1enh-URLLC-05] on other aspects for URLLC and IIoT | Moderator (LG Electronics) |
| R1-2104126 | Final Summary of [104b-e-NR-L1enh-URLLC-05] on other aspects for URLLC and IIoT | Moderator (LG Electronics) |
| R1-2104132 | Summary of email discussion [104b-e-NR-L1enh-URLLC-01] on remaining issues on PDCCH enhancements | Moderator (Huawei) |
| R1-2104133 | Correction on DMRS reception and transmission procedure in TS 38.214 | Moderator (Huawei), ZTE |
| R1-2104134 | Correction on UE procedure for determining physical downlink control channel assignment for Rel-16 PDCCH monitoring capability | Moderator (Huawei), Ericsson |
| R1-2104135 | Corrections on parameter of MCS table set to qam256 | Moderator (Huawei), vivo |
| 7.2.6 | Maintenance of Enhancements on MIMO for NR | |
| R1-2102373 | Text proposals for M-TRP transmission | OPPO |
| R1-2102374 | Corrections for SCell BFR | OPPO |
| R1-2102595 | Maintenance of Multi-beam enhancement operation | CATT |
| R1-2102596 | Maintenance of Multi-TRP transmission | CATT |
| R1-2102657 | Maintenance of multi-beam operation | ZTE |
| R1-2102658 | Maintenance of Multi-TRP enhancements | ZTE |
| R1-2102946 | Maintenance on multi beam related issues | vivo |
| R1-2102947 | Maintenance on multi TRP | vivo |
| R1-2103084 | Remaining issues on Rel-16 beam management enhancement | Apple |
| R1-2103085 | Remaining issues on Rel-16 Multi-TRP enhancement | Apple |
| R1-2103145 | Remaining Issues on Multi-TRP Enhancements | Qualcomm Incorporated |
| R1-2103217 | Summary for Rel.16 NR eMIMO maintenance | Moderator (Samsung) |
| R1-2103218 | On Rel.16 multi-TRP/panel transmission | Samsung |
| R1-2103219 | On UL full power transmission and multi-beam | Samsung |
| R1-2103395 | Corrections on the precoding for PUSCH | Huawei, HiSilicon |
| R1-2103402 | Correction on CPU occupation rules for L1-SINR reporting | Huawei, HiSilicon |
| R1-2103433 | Maintenance of Rel-16 Multi-TRP operation | Nokia, Nokia Shanghai Bell |
| R1-2103551 | Draft CR on DL SPS based PDSCH repetitions | Ericsson |
| R1-2103552 | Maintenance for single-DCI based multi-TRP in Rel-16 | Ericsson |
| R1-2103673 | Interoperation between cross-carrier scheduling and multiple TRPs | ASUSTEK COMPUTER (SHANGHAI) |
| R1-2103879 | Maintenance of Multi-beam enhancement operation | CATT |
| R1-2103976 | Session notes for 7.2.6 (Maintenance of Enhancements on MIMO for NR) | Ad-hoc Chair (Samsung) |
| R1-2103991 | TP for Email Thread 104bis-e-NR-eMIMO-02 | Moderator (Apple Inc.), Huawei, HiSilicon, CATT, vivo |
| R1-2104002 | Corrections for separate HARQ-ACK feedback of multi-TRP transmission | Moderator (OPPO), Apple Inc |
| R1-2104003 | Summary of [104bis-e-NR-eMIMO-03] Email Discussion | Moderator (OPPO) |
| R1-2104004 | Summary of [104bis-e-NR-eMIMO-04] Email Discussion | Moderator (OPPO) |
| R1-2104144 | Summary of [104bis-e-NR-eMIMO-01] Email Discussion | Moderator (Apple) |
| R1-2104145 | Summary of [104bis-e-NR-eMIMO-02] Email Discussion | Moderator (Apple) |
| 7.2.7 | Maintenance of UE Power Saving for NR | |
| R1-2103086 | Maintenance of UE power saving for NR | Apple |
| R1-2103602 | Remaining issues of Rel-16 power saving | ZTE,Sanechips |
| R1-2103748 | Remaining issues for Rel-16 UE power saving | Huawei, HiSilicon |
| R1-2104054 | Final Summary of Email Discussion [104b-e-NR-UE_Pow_Sav-01] Rel-16 UE power saving | Moderator (CATT) |
| 7.2.8 | Maintenance of NR positioning support | |
| R1-2102347 | Correction to the procedure to determine the cell of PRS | Huawei, HiSilicon |
| R1-2102375 | Text Proposals on NR Positioning | OPPO |
| R1-2102597 | Discussion and TP on remaining issues in NR positioning | CATT |
| R1-2102659 | Maintenance of NR positioning support | ZTE |
| R1-2102948 | Maintenance on Rel-16 NR positioning | vivo |
| R1-2103734 | Maintenance on Rel-16 NR positioning | Ericsson |
| R1-2103793 | Summary of Remaining Opens for Rel.16 NR Positioning Maintenance | Moderator (Intel Corporation) |
| R1-2103977 | Session notes for 7.2.8 (Maintenance of NR positioning support) | Ad-Hoc Chair (Ericsson) |
| R1-2104021 | Summary of Email Discussion [104b-e-NR-Pos-01] on NR Positioning Maintenance | Moderator (Intel Corporation) |
| R1-2104022 | Draft CR Correction to the DL PRS reception procedure for PRS cell determination | Moderator (Intel Corporation), Huawei, HiSilicon |
| R1-2104048 | Output #1 for email discussion [104-be-NR-Pos-02] | Moderator (Ericsson) |
| R1-2104049 | CR on the number of pathloss estimates maintained by the UE for SRS for positioning | Moderator (Ericsson), CATT |
| R1-2104065 | Correction to the DL PRS reception procedure for PRS cell determination | Moderator (Intel Corporation), Huawei, HiSilicon |
| 7.2.9 | Maintenance of NR Mobility Enhancements | |
| R1-2103146 | Draft CR to TS 38.213 on clarifying DAPS HO impact on PUCCH repetition counting | Qualcomm Incorporated |
| R1-2103880 | Email discussion summary for NR mobility enhancement | Moderator (Intel Corporation) |
| R1-2103940 | CR to TS 38.213 on clarifying DAPS HO impact on PUCCH repetition counting | Qualcomm Incorporated |
| R1-2104000 | Session notes for 7.2.9 (Maintenance of NR Mobility Enhancements) | Ad-hoc Chair (Ericsson) |
| 7.2.10 | Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements (LTE, NR) | |
| R1-2102489 | Remaining Issues of Power Sharing for NR-DC | ZTE |
| R1-2102683 | Remaining issues on Rel-16 carrier aggregation | MediaTek Inc. |
| R1-2102709 | On removal of p-NR-FR2 from NR-NR DC power control | Nokia, Nokia Shanghai Bell |
| R1-2102949 | Maintenance on NR-DC power control | vivo |
| R1-2103147 | Remaining issue on Multi-RAT Dual-Connectivity and Carrier Aggregation | Qualcomm Incorporated |
| R1-2103641 | Maintenance for Rel-16 MR-DC and CA enhancements | Ericsson |
| R1-2103676 | MR-DC/CA maintenance prep-week summary | Moderator (Nokia) |
| R1-2103754 | Correction on MR-DC Uplink Power Control in 38.213 | Huawei, HiSilicon |
| R1-2103898 | Feature lead summary #1 on UL Power Control for NN-DC | Moderator (Apple) |
| R1-2103966 | Feature lead summary #2 on UL Power Control for NN-DC | Moderator (Apple) |
| R1-2103978 | Session notes for 7.2.10 (Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements) | Ad-Hoc Chair (Ericsson) |
| R1-2104018 | Further Reply LS on power control for NR-DC | RAN1, Apple |
| R1-2104019 | Correction on MR-DC Uplink Power Control in 38.213 | Moderator (Apple), Huawei, HiSilicon |
| R1-2104036 | [104b-e-NR-MRDC-CA-02] Email discussion on cross-carrier A-CSI RS triggering with different SCS | Moderator (Nokia) |
| R1-2104037 | 38.214 CR on CSI request constraint per slot | Moderator (Nokia), vivo, MediaTek |
| 7.2.11 | NR Rel-16 UE Features | |
| R1-2102490 | Discussion on NR Rel-16 UE Features | ZTE |
| R1-2102557 | Discussion on NR Rel-16 UE Features | OPPO |
| R1-2102950 | Remaining issues on Rel-16 eMIMO UE features. | vivo |
| R1-2103087 | Discussions on NR Rel-16 UE features | Apple |
| R1-2103148 | Discussion on NR Rel-16 UE features | Qualcomm Incorporated |
| R1-2103197 | Remaining issues on NR Rel-16 UE features | Nokia, Nokia Shanghai Bell |
| R1-2103399 | Remaining details of Rel-16 NR UE features | Huawei, HiSilicon |
| R1-2103603 | Summary on Rel-16 UE features related discussion | Moderator (NTT DOCOMO INC.) |
| R1-2103662 | Remaining details of Rel-16 NR UE features | Ericsson |
| R1-2103811 | Summary on [104b-e-NR-UEFeature-URLLCIIoT-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2103812 | Summary on [104b-e-NR-UEFeature-MRDCCA-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2103813 | Summary on [104b-e-NR-UEFeature-Others-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2103938 | Updated RAN1 UE features list for Rel-16 NR after RAN1#104bis-e | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2103939 | LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#104bis-e | RAN1, NTT DOCOMO, AT&T |
| R1-2103968 | Summary of NR UE features for eMIMO | Moderator (AT&T) |
| R1-2103969 | Summary of email discussion/approval [104b-e-NR-UEFeatures-eMIMO-01] | Moderator (AT&T) |
| R1-2104120 | Updated RAN1 UE features list for Rel-16 NR after RAN1#104bis-e | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2104121 | LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#104bis-e | RAN1, NTT DOCOMO, AT&T |
| 7.2.12 | Other | |
| R1-2102376 | Enhancement on uplink power control for M-TRP | OPPO |
| R1-2102377 | Text Proposals for Tx Switching between Two Uplink Carriers | OPPO |
| R1-2102491 | Remaining Issues of Rel-16 UL Tx Switching | ZTE |
| R1-2102492 | Remaining Issues of Half-duplex CA | ZTE |
| R1-2102585 | Correction on half-duplex operation in CA with unpaired spectrum | CATT |
| R1-2102586 | Discussion on SSB resources for RLM | CATT |
| R1-2102951 | Discussion on Configuration for CA Half duplex operation | vivo |
| R1-2103149 | Remaining issues for 1Tx-2Tx switching | Qualcomm Incorporated |
| R1-2103457 | TP for 38.214 alignment CR | NEC |
| R1-2103502 | Summary of Rel-16 uplink Tx switching | Moderator (China Telecom) |
| R1-2103601 | Summary on Rel-16 TEI related discussion | Moderator (NTT DOCOMO INC.) |
| R1-2103647 | Maintenance for other Rel16 topics | Ericsson |
| R1-2103719 | Correction of round trip delay drift rate for NTN scenarios | Nokia, Nokia Shanghai Bell, Thales |
| R1-2103720 | Correction of round trip delay drift rate for NTN scenarios | Nokia, Nokia Shanghai Bell, Thales |
| R1-2103746 | Discussion on the remaining problems of supporting Tx switching between two uplink carriers | Huawei, HiSilicon |
| R1-2103747 | Correction on RIM RS resource and set ID mapping | Huawei, HiSilicon |
| R1-2103814 | Summary on [104b-e-NR-Rel16-TEI-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2103815 | Summary on [104b-e-NR-Rel16-TEI-02] | Moderator (NTT DOCOMO, INC.) |
| R1-2103936 | TP on round trip delay drift rate for NTN scenarios | Moderator (NTT DOCOMO, INC.), Nokia, Nokia Shanghai Bell, Thales |
| R1-2103937 | Correction on RIM RS resource and set ID mapping | Moderator (NTT DOCOMO, INC.), Huawei, HiSilicon, CATT, Intel |
| R1-2104005 | [104b-e-NR-Rel16-TxSwitching-01] Summary of email discussion on maintenance of Rel-16 uplink Tx switching | Moderator (China Telecom) |
| R1-2104010 | Correction on half-duplex operation in CA with unpaired spectrum | Moderator (NTT DOCOMO, INC.), Huawei, HiSilicon, CATT |
| R1-2104011 | [draft] Reply LS on half-duplex operation | Huawei |
| R1-2104024 | LS on correction of round trip delay drift rate for NTN scenarios in TR38.821 | RAN1, Nokia |
| R1-2104122 | Reply LS on half-duplex operation | RAN1, Huawei |
| 8.1 | Further enhancements on MIMO for NR | |
| R1-2103979 | Session notes for 8.1 (Further enhancements on MIMO for NR) | Ad-hoc Chair (Samsung) |
| R1-2104138 | Session notes for 8.1 (Further enhancements on MIMO for NR) | Ad-hoc Chair (Samsung) |
| 8.1.1 | Enhancements on Multi-beam Operation | |
| R1-2102333 | Enhancements on multi-beam operation | Huawei, HiSilicon |
| R1-2102378 | Enhancements on Multi-beam Operation | OPPO |
| R1-2102432 | Remaining Issues on Multi-beam Operation | InterDigital, Inc. |
| R1-2102441 | Enhancements on Multi-beam Operation | Spreadtrum Communications |
| R1-2102506 | Further discussion on multi beam enhancement | vivo |
| R1-2102598 | Discussions on enhancements on multi-beam operation | CATT |
| R1-2102660 | Enhancements on Multi-beam Operation | ZTE |
| R1-2102675 | Enhancement on multi-beam operation | MediaTek Inc. |
| R1-2102712 | Enhancements on Multi-beam Operation | Fujitsu |
| R1-2102725 | Discussion on Enhancements for Multi-beam Operation | Asia Pacific Telecom, FGI |
| R1-2102767 | Enhancement on multi-beam operation | FUTUREWEI |
| R1-2102808 | Enhancements on multi-beam operation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2102838 | Enhancements on Multi-beam Operation | Lenovo, Motorola Mobility |
| R1-2102877 | Enhancements on multi-beam operation | CMCC |
| R1-2102954 | Enhancements on Multi-beam Operation | Ericsson |
| R1-2102959 | Enhancements on multi-beam operation | Xiaomi |
| R1-2103014 | Enhancements to Multi-Beam Operations | Intel Corporation |
| R1-2103088 | Views on Rel-17 Beam Management enhancement | Apple |
| R1-2103150 | Enhancements on Multi-beam Operation | Qualcomm Incorporated |
| R1-2103220 | Moderator summary for multi-beam enhancement | Moderator (Samsung) |
| R1-2103221 | Multi-Beam Enhancements | Samsung |
| R1-2103287 | Further enhancement on multi-beam operation | Sony |
| R1-2103365 | Enhancements on Multi-beam Operation | Nokia, Nokia Shanghai Bell |
| R1-2103408 | Enhancements on Multi-beam Operation | Convida Wireless |
| R1-2103440 | Enhancements on multi-beam operation | AT&T |
| R1-2103504 | Enhancements on Multi-beam Operation | LG Electronics |
| R1-2103521 | Discussion on multi-beam operation | NEC |
| R1-2103559 | Discussion on multi-beam operation | NTT DOCOMO, INC. |
| R1-2103637 | Discussion on multi-beam operation | ASUSTeK |
| R1-2103830 | Moderator summary for offline discussion on multi-beam enhancement: SSB and SRS as QCL Type-D source RS | Moderator (Samsung) |
| R1-2103854 | Moderator summary#2 for multi-beam enhancement: Round 1 | Moderator (Samsung) |
| R1-2103892 | Moderator summary#3 for multi-beam enhancement: Round 2 | Moderator (Samsung) |
| R1-2103930 | Moderator summary#4 for multi-beam enhancement: Round 3 | Moderator (Samsung) |
| R1-2103953 | Moderator summary#5 for multi-beam enhancement: Round 4 | Moderator (Samsung) |
| R1-2104141 | DRAFT LS on Timing Assumption for Inter-Cell DL Measurement, Samsung | Samsung |
| R1-2104142 | LS on Timing Assumption for Inter-Cell DL Measurement | RAN1, Samsung |
| R1-2104143 | Moderator summary for LS to RAN4 on Timing Assumption for Inter-Cell DL Measurement | Moderator (Samsung) |
| 8.1.2.1 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | |
| R1-2102334 | Enhancements on multi-TRP for reliability and robustness in Rel-17 | Huawei, HiSilicon |
| R1-2102379 | Enhancements on Multi-TRP based enhancement for PDCCH, PUCCH and PUSCH | OPPO |
| R1-2102433 | Views on PDCCH, PUCCH, and PUSCH Enhancements for M-TRP | InterDigital, Inc. |
| R1-2102442 | Discussion on enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Spreadtrum Communications |
| R1-2102507 | Further discussion on Multi-TRP for PDCCH, PUCCH and PUSCH enhancements | vivo |
| R1-2102568 | Enhancements on Multi-TRP for PUSCH | CAICT |
| R1-2102599 | Discussion on multi-TRP/panel for PDCCH, PUCCH and PUSCH | CATT |
| R1-2102661 | Multi-TRP enhancements for PDCCH, PUCCH and PUSCH | ZTE |
| R1-2102676 | Enhancements on Multi-TRP for PDCCH, PUSCH and PUCCH | MediaTek Inc. |
| R1-2102713 | Enhancements on Multi-TRP for PDCCH PUCCH and PUSCH | Fujitsu |
| R1-2102726 | Discussion on enhancements on multi-TRP for uplink channels | Asia Pacific Telecom, FGI |
| R1-2102761 | Multi-TRP/panel for non-PDSCH | FUTUREWEI |
| R1-2102807 | On multi-TRP enhancements for PDCCH and PUSCH | Fraunhofer IIS, Fraunhofer HHI |
| R1-2102839 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Lenovo, Motorola Mobility |
| R1-2102878 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | CMCC |
| R1-2102960 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Xiaomi |
| R1-2103015 | Multi-TRP enhancements for PDCCH, PUCCH and PUSCH | Intel Corporation |
| R1-2103089 | Views on Rel-17 multi-TRP reliability enhancement | Apple |
| R1-2103151 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Qualcomm Incorporated |
| R1-2103222 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Samsung |
| R1-2103288 | Considerations on Multi-TRP for PDCCH, PUCCH, PUSCH | Sony |
| R1-2103366 | Enhancements for Multi-TRP URLLC schemes | Nokia, Nokia Shanghai Bell |
| R1-2103409 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Convida Wireless |
| R1-2103470 | Enhancements on Multi-TRP for PUSCH | Sharp |
| R1-2103505 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | LG Electronics |
| R1-2103522 | Discussion on multi-TRP for PDCCH, PUCCH and PUSCH | NEC |
| R1-2103550 | On PDCCH, PUCCH and PUSCH enhancements for multi-TRP | Ericsson |
| R1-2103560 | Discussion on MTRP for reliability | NTT DOCOMO, INC. |
| R1-2103660 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | TCL Communication Ltd. |
| R1-2103674 | Discussion on enhancements for Multi-TRP PDCCH | ASUSTeK |
| R1-2103819 | Summary #1 of email discussions [104b-e-NR-feMIMO-02] for mTRP PDCCH enhancements | Moderator (Qualcomm) |
| R1-2103820 | Summary #2 of email discussions [104b-e-NR-feMIMO-02] for mTRP PDCCH enhancements | Moderator (Qualcomm) |
| R1-2103843 | Summary #1 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| R1-2103844 | Summary #2 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| R1-2103845 | Summary #3 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| R1-2103915 | Summary #3 of email discussions [104b-e-NR-feMIMO-02] for mTRP PDCCH enhancements | Moderator (Qualcomm) |
| R1-2104052 | Summary #4 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| 8.1.2.2 | Enhancements on Multi-TRP inter-cell operation | |
| R1-2102335 | Enhancements on inter-cell multi-TRP operations in Rel-17 | Huawei, HiSilicon |
| R1-2102380 | Enhancement on inter-cell multi-TRP operation | OPPO |
| R1-2102434 | Remaining Issues for M-TRP Inter-cell Operation | InterDigital, Inc. |
| R1-2102443 | Discussion on enhancement multi-TRP inter-cell operation | Spreadtrum Communications |
| R1-2102508 | Further discussion on inter-cell MTRP operation | vivo |
| R1-2102600 | Discussion on inter-cell operation for multi-TRP/panel | CATT |
| R1-2102662 | Discussion on Multi-TRP inter-cell operation | ZTE |
| R1-2102762 | Inter-cell multi-TRP operation | FUTUREWEI |
| R1-2102840 | Enhancements on Multi-TRP inter-cell operation | Lenovo, Motorola Mobility |
| R1-2102879 | Enhancements on Multi-TRP inter-cell operation | CMCC |
| R1-2102961 | Enhancement on Inter-cell Multi-TRP operations | Xiaomi |
| R1-2103016 | Multi-TRP enhancements for inter-cell operation | Intel Corporation |
| R1-2103090 | Views on Rel-17 Inter-cell multi-TRP operation | Apple |
| R1-2103152 | Enhancements on Multi-TRP inter-cell operation | Qualcomm Incorporated |
| R1-2103223 | Enhancements on Multi-TRP inter-cell operation | Samsung |
| R1-2103289 | Considerations on inter-cell operation | Sony |
| R1-2103367 | Enhancements to enable inter-cell multi-TRP operations | Nokia, Nokia Shanghai Bell |
| R1-2103506 | Enhancements on Multi-TRP inter-cell operation | LG Electronics |
| R1-2103561 | Discussion on inter-cell multi-TRP operations | NTT DOCOMO, INC. |
| R1-2103715 | On Multi-TRP inter-cell operation | Ericsson |
| R1-2103832 | Feature lead summary#1 on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| R1-2103889 | Feature lead summary#2 on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| R1-2104025 | Feature lead summary#3 on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| R1-2104082 | Feature lead summary#4 on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| 8.1.2.3 | Enhancements on beam management for multi-TRP | |
| R1-2102336 | Discussion on Multi-panel reception for multi-TRP in Rel-17 | Huawei, HiSilicon |
| R1-2102381 | Enhancements on beam management for multi-TRP | OPPO |
| R1-2102435 | On Beam Management Enhancements for M-TRP | InterDigital, Inc. |
| R1-2102444 | Discussion on enhancements on beam management for multi-TRP | Spreadtrum Communications |
| R1-2102509 | Further discussion on MTRP multibeam enhancement | vivo |
| R1-2102601 | Discussion on beam management enhancements for multi-TRP | CATT |
| R1-2102663 | Enhancements on beam management for Multi-TRP | ZTE |
| R1-2102677 | Enhancement on beam management for MTRP | MediaTek Inc. |
| R1-2102714 | Enhancements on beam management for multi-TRP | Fujitsu |
| R1-2102727 | Discussion of enhancements on beam management for Multi-TRP | Asia Pacific Telecom, FGI |
| R1-2102763 | Beam management for simultaneous multi-TRP transmission with multi-panel reception | FUTUREWEI |
| R1-2102841 | Enhancements on beam management for multi-TRP | Lenovo, Motorola Mobility |
| R1-2102880 | Enhancements on beam management for multi-TRP | CMCC |
| R1-2102962 | Enhancement on beam management for Multi-TRP | Xiaomi |
| R1-2103017 | Multi-TRP enhancements for beam management | Intel Corporation |
| R1-2103091 | Views on Rel-17 multi-TRP BM enhancement | Apple |
| R1-2103153 | Enhancements on beam management for multi-TRP | Qualcomm Incorporated |
| R1-2103224 | Enhancements on beam management for multi-TRP | Samsung |
| R1-2103290 | Considerations on beam management for multi-TRP | Sony |
| R1-2103324 | Enhancements on beam management for multi-TRP | ETRI |
| R1-2103368 | Enhancements on Beam Management for Multi-TRP/Panel Transmission | Nokia, Nokia Shanghai Bell |
| R1-2103410 | On multi-TRP BFR | Convida Wireless |
| R1-2103441 | Enhancements on beam management for multi-TRP | AT&T |
| R1-2103507 | Enhancements on beam management for multi-TRP | LG Electronics |
| R1-2103523 | Discussion on beam management for multi-TRP | NEC |
| R1-2103545 | On beam management enhancements for simultaneous multi-TRP transmission with multi-panel reception | Ericsson |
| R1-2103562 | Discussion on beam management for MTRP | NTT DOCOMO, INC. |
| R1-2103630 | Discussion on beam management for multi-TRP | ITRI |
| R1-2103661 | Enhancements on beam management for multi-TRP | TCL Communication Ltd. |
| R1-2103858 | Moderator summary #1 on M-TRP simultaneous transmission with multiple Rx panels | Moderator (CATT) |
| R1-2103906 | Moderator summary #2 on M-TRP simultaneous transmission with multiple Rx panels | Moderator (CATT) |
| R1-2103996 | Moderator summary #3 on M-TRP simultaneous transmission with multiple Rx panels | Moderator (CATT) |
| 8.1.2.4 | Enhancements on HST-SFN deployment | |
| R1-2102337 | Enhancements on high speed train for multi-TRP in Rel-17 | Huawei, HiSilicon |
| R1-2102382 | Enhancements on HST-SFN deployment | OPPO |
| R1-2102436 | Multi-TRP Transmission for HST-SFN | InterDigital, Inc. |
| R1-2102445 | Discussion on enhancements on HST-SFN deployment | Spreadtrum Communications |
| R1-2102510 | Further discussion and evaluation on HST-SFN schemes | vivo |
| R1-2102602 | Enhancements for HST-SFN deployment | CATT |
| R1-2102664 | Discussion on Multi-TRP HST enhancements | ZTE |
| R1-2102728 | Discussion of enhancements on HST-SFN deployment | Asia Pacific Telecom, FGI |
| R1-2102764 | Enhancement to support HST-SFN deployment scenario | FUTUREWEI |
| R1-2102881 | Enhancements on HST-SFN deployment | CMCC |
| R1-2102963 | Enhancements on HST-SFN operation for multi-TRP PDCCH transmission | Xiaomi |
| R1-2103018 | Enhancements to HST-SFN deployments | Intel Corporation |
| R1-2103092 | Views on Rel-17 HST enhancement | Apple |
| R1-2103154 | Enhancements on HST-SFN deployment | Qualcomm Incorporated |
| R1-2103198 | Enhancement on HST-SFN deployment | Ericsson |
| R1-2103225 | Enhancements on HST-SFN | Samsung |
| R1-2103291 | Considerations on HST-SFN operation for multi-TRP | Sony |
| R1-2103369 | Enhancements for HST-SFN deployment | Nokia, Nokia Shanghai Bell |
| R1-2103508 | Enhancements on HST-SFN deployment | LG Electronics |
| R1-2103524 | Discussion on HST-SFN deployment | NEC |
| R1-2103563 | Discussion on HST-SFN deployment | NTT DOCOMO, INC. |
| R1-2103606 | Enhancements for HST-SFN deployment | Lenovo, Motorola Mobility |
| R1-2103855 | Summary#1 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2103893 | Summary#2 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2103902 | Draft LS on TCI states indication for PDCCH | Intel Corporation |
| R1-2104020 | Summary#3 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2104064 | LS on TCI states indication for PDCCH | RAN1, Intel Corporation |
| R1-2104068 | Summary#4 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| 8.1.3 | Enhancements on SRS flexibility, coverage and capacity | |
| R1-2102338 | SRS Enhancements in Rel-17 | Huawei, HiSilicon |
| R1-2102383 | Enhancements on SRS flexibility, coverage and capacity | OPPO |
| R1-2102437 | Enhanced SRS Transmission and Antenna Switching | InterDigital, Inc. |
| R1-2102446 | Consideration on SRS enhancement | Spreadtrum Communications |
| R1-2102511 | Further discussion on SRS enhancement | vivo |
| R1-2102603 | Enhancements on Rel-17 SRS | CATT |
| R1-2102665 | Enhancements on SRS flexibility, coverage and capacity | ZTE |
| R1-2102674 | FL summary #1 on SRS enhancements | Moderator (ZTE) |
| R1-2102678 | Enhancements on SRS flexibility, coverage and capacity | MediaTek Inc. |
| R1-2102765 | Enhancements on SRS flexibility, coverage and capacity | FUTUREWEI |
| R1-2102842 | Enhancements on SRS | Lenovo, Motorola Mobility |
| R1-2102882 | Enhancements on SRS flexibility, coverage and capacity | CMCC |
| R1-2102964 | Discussion on SRS enhancements | Xiaomi |
| R1-2103019 | Discussion on SRS enhancements | Intel Corporation |
| R1-2103093 | Views on Rel-17 SRS enhancement | Apple |
| R1-2103155 | Enhancements on SRS flexibility, coverage and capacity | Qualcomm Incorporated |
| R1-2103226 | Enhancements on SRS | Samsung |
| R1-2103292 | Considerations on SRS flexibility, coverage and capacity | Sony |
| R1-2103370 | Enhancements on SRS flexibility, coverage and capacity | Nokia, Nokia Shanghai Bell |
| R1-2103444 | SRS Performance and Potential Enhancements | Ericsson |
| R1-2103471 | Enhancements on SRS | Sharp |
| R1-2103509 | Enhancements on SRS flexibility, coverage and capacity | LG Electronics |
| R1-2103525 | Discussion on SRS enhancement | NEC |
| R1-2103564 | Discussion on SRS enhancement | NTT DOCOMO, INC. |
| R1-2103679 | Enhancements on SRS for coverage and capacity | Fraunhofer IIS, Fraunhofer HHI |
| R1-2103878 | FL summary #2 on SRS enhancements | Moderator (ZTE) |
| R1-2103928 | FL summary#3 on SRS enhancements | Moderator (ZTE) |
| 8.1.4 | CSI enhancements: MTRP and FR1 FDD reciprocity | |
| R1-2102339 | Discussion on CSI Enhancements for Rel-17 | Huawei, HiSilicon, China Unicom |
| R1-2102384 | CSI enhancement for M-TRP and FDD reciprocity | OPPO |
| R1-2102438 | Further Discussion on CSI Enhancements for NCJT MTRP | InterDigital, Inc. |
| R1-2102447 | Discussion on CSI enhancement for multi-TRP and FR1 FDD reciprocity | Spreadtrum Communications |
| R1-2102512 | Further discussion and evaluation on MTRP CSI and Partial reciprocity | vivo |
| R1-2102604 | Discussion on CSI enhancements for mTRP and FDD reciprocity | CATT |
| R1-2102666 | CSI enhancements for Multi-TRP and FR1 FDD reciprocity | ZTE |
| R1-2102679 | CSI enhancement for NCJT and FR1 FDD reciprocity | MediaTek Inc. |
| R1-2102766 | CSI enhancement for multi-TRP and FDD | FUTUREWEI |
| R1-2102810 | CSI enhancements on Type II PS codebook and multi-TRP | Fraunhofer IIS, Fraunhofer HHI |
| R1-2102883 | Enhancements on CSI reporting for Multi-TRP | CMCC |
| R1-2103020 | On CSI enhancements for MTRP and FDD | Intel Corporation |
| R1-2103094 | Views on Rel-17 CSI enhancement | Apple |
| R1-2103156 | CSI enhancements: MTRP and FR1 FDD reciprocity | Qualcomm Incorporated |
| R1-2103227 | Views on Rel. 17 CSI enhancements | Samsung |
| R1-2103293 | Additional considerations on CSI enhancements | Sony |
| R1-2103371 | Enhancement on CSI measurement and reporting | Nokia, Nokia Shanghai Bell |
| R1-2103510 | CSI enhancements for Rel-17 | LG Electronics |
| R1-2103526 | Discussion on CSI enhancement for multi-TRP | NEC |
| R1-2103543 | CSI enhancements for Multi-TRP and FR1 FDD reciprocity | Ericsson |
| R1-2103565 | Discussion on CSI enhancements | NTT DOCOMO, INC. |
| R1-2103607 | CSI enhancements for multi-TRP and FDD reciprocity | Lenovo, Motorola Mobility |
| R1-2103828 | Views on Rel-17 CSI enhancements | Samsung |
| R1-2103870 | Summary of CSI enhancements for MTRP and FDD (Round 0) | Moderator (Huawei) |
| R1-2103871 | Summary of CSI enhancements for MTRP and FDD (Round 1) | Moderator (Huawei) |
| R1-2103872 | Summary of CSI enhancements for MTRP and FDD (Round 2) | Moderator (Huawei) |
| R1-2103965 | Summary of CSI enhancements for MTRP and FDD (Round 3) | Moderator (Huawei) |
| R1-2104028 | Summary of CSI enhancements for MTRP and FDD (Round 4) and NWM Discussion | Moderator (Huawei) |
| 8.1.5 | Other | |
| R1-2102439 | Performance Evaluation of Multi-Panel UE in a Multi-TRP Deployment | InterDigital, Inc. |
| R1-2102479 | Discussion on further enhancements for multi-beam operation | OPPO |
| R1-2102513 | Discussion on L1 L2 inter-cell mobility | vivo |
| R1-2102605 | Evaluation for HST-SFN deployment | CATT |
| R1-2102667 | Further details on Multi-beam and Multi-TRP operation | ZTE |
| R1-2102843 | HARQ feedback of SPS PDSCH reception in multi-DCI based multiple TRPs | Lenovo, Motorola Mobility |
| R1-2103095 | Views on MIMO enhancement | Apple |
| R1-2103228 | Additional enhancements for multi-beam | Samsung |
| R1-2103394 | Further considerations and simulations for Rel-17 PS codebook design | Huawei, HiSilicon, China Unicom |
| R1-2103511 | Analysis on TRP- and/or UE panel-specific UL timing synchronization | LG Electronics |
| R1-2103566 | Discussion on UL dense deployment | NTT DOCOMO, INC. |
| R1-2103667 | On Rel.18 MIMO work item proposals | Ericsson |
| R1-2103668 | On Rel.18 MIMO work item proposals | Ericsson |
| 8.2 | Supporting NR from 52.6GHz to 71 GHz | |
| R1-2103980 | Session notes for 8.2 (Extending current NR operation to 71GHz) | Ad-Hoc Chair (Ericsson) |
| 8.2.1 | Initial access aspects | |
| R1-2102327 | Initial access signals and channels for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2102385 | Discussion on initial access aspects | OPPO |
| R1-2102448 | Discussion on initial access aspects for NR for 60GHz | Spreadtrum Communications |
| R1-2102514 | Discussions on initial access aspects for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2102558 | Initial access aspects | Nokia, Nokia Shanghai Bell |
| R1-2102621 | Initial access aspects for up to 71GHz operation | CATT |
| R1-2102688 | Discussion on initial access of 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2102715 | Considerations on initial access for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2102772 | Further considerations on initial access for additional SCS in Beyond 52.6GHz | FUTUREWEI |
| R1-2102788 | Initial Access Aspects | Ericsson |
| R1-2102977 | On initial access aspects for NR from 52.6GHz to 71GHz | Xiaomi |
| R1-2102996 | Initial access aspects for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2103021 | Discussion on initial access aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2103096 | Discussion on Initial access signals and channels | Apple |
| R1-2103157 | Initial access aspects for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2103229 | Initial access aspects for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2103294 | Considerations on initial access aspects for NR from 52.6 GHz to 71 GHz | Sony |
| R1-2103339 | Initial access aspects to support NR above 52.6 GHz | LG Electronics |
| R1-2103411 | NR Initial Access from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2103442 | Further Discussion of Initial Access Aspects | AT&T |
| R1-2103448 | Discussions on initial access aspects | InterDigital, Inc. |
| R1-2103472 | Initial access aspects | Sharp |
| R1-2103487 | Discussion on the initial access aspects for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2103519 | Discussion on initial access aspects supporting NR from 52.6 to 71 GHz | NEC |
| R1-2103567 | Initial access aspects for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2103691 | Discussion on initial access aspects for NR beyond 52.6GHz | WILUS Inc. |
| R1-2103801 | Issue Summary for initial access aspects of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2103802 | Summary #1 of email discussion on initial access aspects of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2104029 | Summary #2 of email discussion on initial access aspects of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2104124 | Summary #3 of email discussion on initial access aspects of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| 8.2.2 | PDCCH monitoring enhancements | |
| R1-2102328 | Enhancement on PDCCH monitoring | Huawei, HiSilicon |
| R1-2102386 | Discussion on PDCCH monitoring | OPPO |
| R1-2102449 | Discussion on PDCCH monitoring enhancement for NR beyond 52.6 GHz | Spreadtrum Communications |
| R1-2102515 | Discussions on PDCCH monitoring enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2102559 | PDCCH monitoring enhancements | Nokia, Nokia Shanghai Bell |
| R1-2102622 | PDCCH monitoring enhancements for up to 71GHz operation | CATT |
| R1-2102704 | PDCCH monitoring enhancement for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2102773 | Further considerations on PDCCH monitoring enhancements | FUTUREWEI |
| R1-2102789 | PDCCH Monitoring Enhancements | Ericsson |
| R1-2102809 | PDCCH monitoring enhancement for NR from 52.6GHz to 71GHz | Panasonic |
| R1-2102978 | PDCCH monitoring enhancement for NR 52.6-71GHz | Xiaomi |
| R1-2102997 | PDCCH monitoring enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2103022 | Discussion on PDCCH monitoring enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2103097 | Discussion on PDCCH Enhancements for above 52.6 GHz | Apple |
| R1-2103158 | PDCCH monitoring enhancements for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2103230 | PDCCH monitoring enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2103295 | PDCCH enhancement for NR from 52.6GHz to 71GHz | Sony |
| R1-2103340 | PDCCH monitoring enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2103412 | PDCCH Monitoring Considerations for Supporting NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2103449 | Discussions on PDCCH monitoring enhancements | InterDigital, Inc. |
| R1-2103488 | Discussion on the PDCCH monitoring enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2103512 | Discussion on PDCCH monitoring enhancements supporting NR from 52.6GHz to 71 GHz | NEC |
| R1-2103568 | PDCCH monitoring enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2103689 | Feature lead summary for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2103933 | Feature lead summary for [104b-e-NR-52-71GHz-02] Email discussion/approval on PDCCH Monitoring Enhancement | Moderator (Lenovo) |
| R1-2104057 | Feature lead summary #2 for [104b-e-NR-52-71GHz-02] Email discussion/approval on PDCCH Monitoring Enhancements | Moderator (Lenovo) |
| 8.2.3 | Enhancements for PUCCH formats 0/1/4 | |
| R1-2102329 | Enhancement on PUCCH formats | Huawei, HiSilicon |
| R1-2102387 | Discussion on enhancements for PUCCH format 0/1/4 | OPPO |
| R1-2102450 | Discussion on enhancements for PUCCH format 0/1/4 for above 52.6GHz | Spreadtrum Communications |
| R1-2102516 | Discussions on PUCCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2102560 | Enhancements for PUCCH formats | Nokia, Nokia Shanghai Bell |
| R1-2102623 | Enhancements for PUCCH formats for up to 71GHz operation | CATT |
| R1-2102706 | On Enhancements for PUCCH formats 0/1/4 | MediaTek Inc. |
| R1-2102774 | Considerations on PUCCH Channel enhancements | FUTUREWEI |
| R1-2102790 | Enhancements for PUCCH formats 0/1/4 | Ericsson |
| R1-2102998 | Enhancements to PUCCH formats 0/1/4 for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2103023 | Discussion on PUCCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2103098 | Discussion on Enhancements for PUCCH formats 0/1/4 | Apple |
| R1-2103159 | Enhancements for PUCCH for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2103231 | Enhancements for PUCCH format 0/1/4 for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2103296 | Considerations on enhancements for PUCCH formats 0/1/4 | Sony |
| R1-2103341 | Enhancements for PUCCH formats 0/1/4 to support NR above 52.6 GHz | LG Electronics |
| R1-2103450 | Discussions on enhancements for PUCCH formats 0/1/4 | InterDigital, Inc. |
| R1-2103489 | Discussion on the PUCCH enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2103569 | PUCCH format 0/1/4 enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2103692 | Discussion on PUCCH enhancement for PUCCH format 0/1/4 | WILUS Inc. |
| R1-2103784 | FL Summary for Enhancements for PUCCH formats 0/1/4 | Moderator (Ericsson) |
| R1-2103869 | Enhancements for PUCCH formats 0/1/4 | Ericsson |
| R1-2104001 | FL Summary 2 for Enhancements for PUCCH formats 0/1/4 | Moderator (Ericsson) |
| R1-2104060 | [DRAFT] LS to RAN4 on maximum UE conducted power and maximum UE EIRP for operation in the 52.6 – 71 GHz band | Ericsson |
| R1-2104061 | LS to RAN4 on maximum UE conducted power and maximum UE EIRP for operation in the 52.6 – 71 GHz band | RAN1, Ericsson |
| 8.2.4 | Beam management for new SCSs | |
| R1-2102330 | Discussion on the beam management procedures for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2102388 | Discussion on beam management | OPPO |
| R1-2102451 | Discussion on beam manangement for above 52.6GHz | Spreadtrum Communications |
| R1-2102517 | Discussions on beam management for new SCSs for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2102561 | Beam Management Aspects | Nokia, Nokia Shanghai Bell |
| R1-2102624 | Beam management for new SCSs for up to 71GHz operation | CATT |
| R1-2102705 | Beam management discussion for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2102775 | Beam management for shared spectrum access in Beyond 52.6GHz | FUTUREWEI |
| R1-2102791 | Beam Management for New SCSs | Ericsson |
| R1-2102979 | Discussion on beam management in NR from 52.6 GHz to 71GHz | Xiaomi |
| R1-2102999 | Beam-management enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2103024 | Discussion on Beam management aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2103099 | Beam Management for New SCSs | Apple |
| R1-2103160 | Beam management for new SCS for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2103232 | Beam management for new SCSs for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2103297 | Beam management enhancement for NR from 52.6GHz to 71GHz | Sony |
| R1-2103342 | Enhancements for beam management to support NR above 52.6 GHz | LG Electronics |
| R1-2103413 | On Beam Management for Supporting NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2103451 | Discussions on beam management for new SCSs | InterDigital, Inc. |
| R1-2103490 | Discussion on the beam management for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2103570 | Beam based operation for new SCSs for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2103821 | FL Summary for Beam Management for new SCSs | Moderator (InterDigital, Inc.) |
| R1-2103911 | Discussion Summary #1 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| R1-2103912 | Discussion Summary #2 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| 8.2.5 | PDSCH/PUSCH enhancements | |
| R1-2102331 | PDSCH/PUSCH enhancements for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2102389 | Discussion on PDSCH/PUSCH enhancements | OPPO |
| R1-2102452 | Discussion on PDSCH and PUSCH enhancements for above 52.6GHz | Spreadtrum Communications |
| R1-2102518 | Discussions on PDSCH/PUSCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2102562 | PDSCH/PUSCH enhancements | Nokia, Nokia Shanghai Bell |
| R1-2102569 | Discussions on scheduling enhancements for PDSCH and PUSCH | CAICT |
| R1-2102625 | PDSCH/PUSCH enhancements for up to 71GHz operation | CATT |
| R1-2102716 | Considerations on multi-PDSCH/PUSCH with a single DCI and HARQ for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2102776 | Considerations on PDSCH/PUSCH enhancements | FUTUREWEI |
| R1-2102792 | PDSCH-PUSCH Enhancements | Ericsson |
| R1-2102980 | PDSCH and PUSCH enhancements for NR 52.6-71GHz | Xiaomi |
| R1-2103000 | PDSCH/PUSCH scheduling enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2103012 | PT-RS enhancements for NR from 52.6GHz to 71GHz | Mitsubishi Electric RCE |
| R1-2103025 | Discussion on PDSCH/PUSCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2103100 | Discussion on PDSCH/PUSCH enhancements for above 52.6 GHz | Apple |
| R1-2103161 | PDSCH/PUSCH enhancements for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2103233 | PDSCH/PUSCH enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2103298 | PDSCH/PUSCH enhancements for NR from 52.6 GHz to 71 GHz | Sony |
| R1-2103343 | PDSCH/PUSCH enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2103344 | Summary #1 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2103407 | Discussion on PDSCH and PUSCH enhancements for 52.6GHz – 71GHZ band | CEWiT |
| R1-2103414 | PDSCH Considerations for Supporting NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2103452 | Discussions on PDSCH/PUSCH enhancements for 52.6 GHz to 71 GHz Band | InterDigital, Inc. |
| R1-2103463 | Discussion on multi-PDSCH/PUSCH scheduling for NR 52.6-71 GHz | Panasonic Corporation |
| R1-2103491 | Discussion on the data channel enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2103513 | Discussion on PDSCH enhancements supporting NR from 52.6GHz to 71 GHz | NEC |
| R1-2103571 | PDSCH/PUSCH enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2103693 | Discussion on multi-PDSCH/PUSCH scheduling for NR from 52.6GHz to 71GHz | WILUS Inc. |
| R1-2103726 | PDSCH-PUSCH Enhancement Aspects for NR beyond 52.6 GHz | Charter Communications |
| R1-2103817 | Summary of PDSCH/PUSCH enhancements (Bandwidth/Timeline/Reference signals) | Moderator (vivo) |
| R1-2103818 | Discussion summary #1 of [104b-e-NR-52-71GHz-05] | Moderator (vivo) |
| R1-2103916 | Discussion summary #2 of [104b-e-NR-52-71GHz-05] | Moderator (vivo) |
| R1-2103927 | Summary #2 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2104041 | Discussion summary #3 of [104b-e-NR-52-71GHz-05] | Moderator (vivo) |
| R1-2104042 | Summary #3 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2104104 | Summary #4 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| 8.2.6 | Channel access mechanism | |
| R1-2102332 | Channel access mechanism for 60 GHz unlicensed operation | Huawei, HiSilicon |
| R1-2102390 | Discussion on channel access mechanism | OPPO |
| R1-2102453 | Discussion on channel access mechanism for above 52.6GHz | Spreadtrum Communications |
| R1-2102519 | Discussions on channel access mechanism for NR operation from 52.6GHz to 71 GHz | vivo |
| R1-2102563 | Channel access mechanism | Nokia, Nokia Shanghai Bell |
| R1-2102570 | Discussions on channel access mechanism enhancements for 52.6G-71 GHz | CAICT |
| R1-2102626 | Channel access mechanism for up to 71GHz operation | CATT |
| R1-2102689 | On the channel access mechanisms for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2102717 | Considerations on channel access mechanism for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2102777 | Further considerations on channel access for shared spectrum Beyond 52.6 GHz | FUTUREWEI |
| R1-2102793 | Channel Access Mechanisms | Ericsson |
| R1-2102981 | Channel access mechanism for NR on 52.6-71 GHz | Xiaomi |
| R1-2103001 | Channel access mechanisms for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2103026 | Discussion on channel access mechanism for extending NR up to 71 GHz | Intel Corporation |
| R1-2103101 | Channel access mechanisms for unlicensed access above 52.6GHz | Apple |
| R1-2103162 | Channel access mechanism for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2103234 | Channel access mechanism for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2103299 | channel access mechanism for 60 GHz unlicensed spectrum | Sony |
| R1-2103345 | Channel access mechanism to support NR above 52.6 GHz | LG Electronics |
| R1-2103415 | Channel Access for Supporting NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2103427 | Channel access for multi-beam operation | Panasonic |
| R1-2103443 | Further Discussion of Channel Access Mechanisms | AT&T |
| R1-2103453 | Discussion on channel access mechanisms | InterDigital, Inc. |
| R1-2103492 | Discussion on the channel access for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2103520 | Discussion on channel access mechanism supporting NR from 52.6 to 71GHz | NEC |
| R1-2103572 | Channel access mechanism for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2103631 | Discussion on multi-beam operation | ITRI |
| R1-2103694 | Discussion on channel access mechanism for NR from 52.6GHz to 71GHz | WILUS Inc. |
| R1-2103727 | Channel access mechanisms for above 52.6 GHz | Charter Communications |
| R1-2103791 | FL summary for channel access mechanism for 52.6GHz to 71GHz | Moderator (Qualcomm) |
| R1-2103941 | FL summary#2 for channel access mechanism for 52.6GHz to 71GHz | Moderator (Qualcomm) |
| R1-2104040 | FL summary#3 for channel access mechanism for 52.6GHz to 71GHz | Moderator (Qualcomm) |
| 8.2.7 | Other | |
| R1-2102391 | Discussion on other aspects | OPPO |
| R1-2102520 | Discussions on frequency range definition and sync raster for 52.6-71GHz | vivo |
| R1-2102564 | Extending current NR operation to 71 GHz | Nokia, Nokia Shanghai Bell |
| R1-2102627 | Views on Frequency Range for 52.6 to 71 GHz | CATT |
| R1-2102794 | NR channelization for 52.6 – 71 GHz band | Ericsson |
| R1-2103102 | On How to Introduce the 52.6-71GHz Frequency Range | Apple |
| R1-2103235 | Discussion on defining frequency range for NR from 52.6 to 71 GHz | Samsung |
| R1-2103346 | Link level evaluation results for NR above 52.6 GHz | LG Electronics |
| R1-2103393 | Link level and system evaluation results for 52-71 GHz | Huawei, HiSilicon |
| R1-2103418 | Discussion on frequency range determination for NR extension up to 71GHz | Intel Corporation |
| R1-2103454 | Efficient beam management for NR in 52.6 – 71 GHz | InterDigital, Inc. |
| R1-2103493 | Discussion on the frequency range definition for above 52.6GHz | ZTE, Sanechips |
| R1-2103573 | Views on how to introduce 52.6 - 71 GHz frequency range in NR | NTT DOCOMO, INC. |
| 8.3.1.1 | UE feedback enhancements for HARQ-ACK | |
| R1-2102351 | UE feedback enhancements for HARQ-ACK | Huawei, China Southern Power Grid, BUPT, HiSilicon |
| R1-2102392 | HARQ-ACK enhancements for Rel-17 URLLC/IIoT | OPPO |
| R1-2102454 | Discussion on HARQ-ACK enhancements for Rel-17 URLLC | Spreadtrum Communications |
| R1-2102493 | Discussion on HARQ-ACK enhancements for eURLLC | ZTE |
| R1-2102521 | HARQ-ACK enahncements for Rel-17 URLLC | vivo |
| R1-2102571 | UE feedback enhancements for HARQ-ACK | CAICT |
| R1-2102628 | UE feedback enhancements for HARQ-ACK | CATT |
| R1-2102694 | On UE feedback enhancements for HARQ-ACK | MediaTek Inc. |
| R1-2102729 | Discussion on UE feedback enhancements for HARQ-ACK | Asia Pacific Telecom, FGI |
| R1-2102744 | HARQ-ACK Enhancements for IIoT/URLLC | Ericsson |
| R1-2102819 | HARQ-ACK Feedback Enhancements for URLLC/IIoT | Nokia, Nokia Shanghai Bell |
| R1-2102825 | Moderator summary #1 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2102867 | Discussion on UE feedback enhancements for HARQ-ACK | China Telecom |
| R1-2102910 | Discussion on UE feedback enhancements for HARQ-ACK | CMCC |
| R1-2102922 | UE feedback enhancement for HARQ-ACK | TCL Communication Ltd. |
| R1-2102982 | UE feedback enhancement for HARQ-ACK | Xiaomi |
| R1-2103027 | Further details on UE HARQ feedback enhancements | Intel Corporation |
| R1-2103103 | Views on URLLC HARQ feedback enhancements | Apple |
| R1-2103163 | HARQ-ACK enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2103200 | HARQ-ACK enhancements for IIoT and URLLC | InterDigital, Inc. |
| R1-2103205 | Discussion on UE feedback enhancements for HARQ-ACK | Panasonic Corporation |
| R1-2103236 | On HARQ-ACK reporting enhancements | Samsung |
| R1-2103300 | Considerations on HARQ-ACK enhancements for URLLC | Sony |
| R1-2103325 | UE feedback enhancements for HARQ-ACK | ETRI |
| R1-2103347 | Discussion on UE feedback enhancement for HARQ-ACK | LG Electronics |
| R1-2103473 | UE feedback enhancements for HARQ-ACK | Sharp |
| R1-2103527 | UE feedback enhancements for HARQ-ACK | NEC |
| R1-2103574 | Discussion on HARQ-ACK feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2103610 | HARQ-ACK feedback enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2103695 | Discussion on HARQ-ACK enhancement for URLLC/IIoT | WILUS Inc. |
| R1-2103882 | Moderator summary #2 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2103883 | Moderator summary #3 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2104038 | Moderator summary #4 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2104039 | Final moderator summary on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| 8.3.1.2 | CSI feedback enhancements | |
| R1-2102352 | CSI feedback enhancements | Huawei, HiSilicon, SIA |
| R1-2102393 | CSI feedback enhancements for URLLC | OPPO |
| R1-2102455 | Discussion on CSI feedback enhancements | Spreadtrum Communications |
| R1-2102494 | Discussion on CSI feedback enhancements for eURLLC | ZTE |
| R1-2102522 | CSI feedback enhancements for Rel-17 URLLC | vivo |
| R1-2102629 | CSI feedback enhancements | CATT |
| R1-2102695 | CSI feedback enhancements for URLLC | MediaTek Inc. |
| R1-2102739 | CSI feedback enhancements | InterDigital, Inc. |
| R1-2102745 | CSI Feedback Enhancements for IIoT/URLLC | Ericsson |
| R1-2102749 | Summary of additional discussions on CSI feedback enhancements for enhanced URLLC/IIoT after RAN1#104-e | Moderator (InterDigital, Inc.) |
| R1-2102759 | CSI feedback enhancements for URLLC | FUTUREWEI |
| R1-2102872 | Discussion on CSI Feedback Enhancements | Quectel, Langbo |
| R1-2102911 | Discussion on CSI feedback enhancements for URLLC | CMCC |
| R1-2103028 | Analysis of enhanced CSI feedback schemes | Intel Corporation |
| R1-2103104 | Views on URLLC CSI feedback enhancements | Apple |
| R1-2103164 | CSI enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2103237 | On Enahncements of CSI Reports for URLLC | Samsung |
| R1-2103301 | Considerations on CSI feedback enhancements | Sony |
| R1-2103348 | Discussion on CSI feedback enhancements for URLLC | LG Electronics |
| R1-2103434 | CSI feedback enhancements for URLLC/IIoT use cases | Nokia, Nokia Shanghai Bell |
| R1-2103575 | Discussion on CSI feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2103611 | CSI feedback enhancements for URLLC/IIoT | Lenovo, Motorola Mobility |
| R1-2103785 | CSI feedback enhancements | InterDigital, Inc. |
| R1-2103786 | Feature lead summary #1 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2103787 | Feature lead summary #2 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2103800 | CSI enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2103955 | Feature lead summary #3 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2103956 | Feature lead summary #4 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| 8.3.2 | Enhancements for unlicensed band URLLC/IIoT | |
| R1-2102354 | Uplink enhancements for URLLC in unlicensed controlled environments | Huawei, China Southern Power Grid, BUPT, HiSilicon |
| R1-2102394 | Enhancements for unlicensed band URLLC/IIoT | OPPO |
| R1-2102456 | Discussion on enhancements for unlicensed band URLLC/IIoT | Spreadtrum Communications |
| R1-2102495 | Discussion on unlicensed band URLLC/IIoT | ZTE |
| R1-2102523 | Enhancements for unlicensed band URLLC/IIoT | vivo |
| R1-2102630 | Enhancements for unlicensed band URLLC/IIoT | CATT |
| R1-2102648 | UL enhancements for IIoT/URLLC in unlicensed controlled environment | Nokia, Nokia Shanghai Bell |
| R1-2102696 | On the enhancements for unlicensed band URLLC/IIoT | MediaTek Inc. |
| R1-2102730 | Enhancements for unlicensed band URLLC/IIoT | Asia Pacific Telecom, FGI |
| R1-2102746 | Enhancements for IIoT/URLLC on Unlicensed Band | Ericsson |
| R1-2102760 | Further considerations on UE initiated COT for FFP | FUTUREWEI |
| R1-2102813 | Enhancements for unlicensed band URLLC/IIoT | NEC |
| R1-2102983 | Enhancement for unlicensed band URLLC/IIoT | Xiaomi |
| R1-2103029 | Further Details on Enabling URLLC/IIoT in Unlicensed Band | Intel Corporation |
| R1-2103105 | URLLC uplink enhancements for unlicensed spectrum | Apple |
| R1-2103165 | Uplink enhancements for URLLC in unlicensed controlled environments | Qualcomm Incorporated |
| R1-2103201 | Enhancements for unlicensed band URLLC/IIoT | InterDigital, Inc. |
| R1-2103206 | Enhancements for unlicensed band URLLC/IIoT | Panasonic Corporation |
| R1-2103238 | Enhancements for unlicensed band URLLC/IIoT | Samsung |
| R1-2103302 | Considerations on unlicensed URLLC | Sony |
| R1-2103326 | Enhancements for unlicensed band URLLC/IIoT | ETRI |
| R1-2103349 | Discussion on unlicensed band URLLC/IIOT | LG Electronics |
| R1-2103474 | Enhancements for unlicensed band URLLC/IIoT | Sharp |
| R1-2103576 | Discussion on enhancements for unlicensed band URLLC | NTT DOCOMO, INC. |
| R1-2103612 | Enhancements for unlicensed band URLLC/IIoT | Lenovo, Motorola Mobility |
| R1-2103696 | Discussion on enhancement for unlicensed URLLC/IIoT | WILUS Inc. |
| R1-2103728 | Unlicensed spectrum operation for URLLC/IIoT | Charter Communications |
| R1-2103849 | Summary#1 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2103850 | Summary#2 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2103851 | Summary#3 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2103852 | Summary#4 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2103960 | Summary#5 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| 8.3.3 | Intra-UE Multiplexing/Prioritization | |
| R1-2102353 | Intra-UE multiplexing enhancements | Huawei, China Southern Power Grid, BUPT, HiSilicon |
| R1-2102395 | Enhancements on intra-UE multiplexing/prioritization | OPPO |
| R1-2102457 | Discussion on intra-UE multiplexing/prioritization | Spreadtrum Communications |
| R1-2102496 | Discussion on enhanced intra-UE multiplexing | ZTE |
| R1-2102524 | Intra-UE Multiplexing/Prioritization for Rel-17 URLLC | vivo |
| R1-2102631 | Intra-UE multiplexing and prioritization | CATT |
| R1-2102697 | Methods for intra-UE multiplexing and prioritization | MediaTek Inc. |
| R1-2102731 | Discussion on Intra-UE multiplexing/prioritization | Asia Pacific Telecom, FGI |
| R1-2102740 | Intra-UE multiplexing and prioritization | InterDigital, Inc. |
| R1-2102747 | Intra-UE Multiplexing/Prioritization Enhancements for IIoT/URLLC | Ericsson |
| R1-2102814 | Discussion on Intra-UE prioritization and multiplexing | NEC |
| R1-2102820 | On UL intra-UE prioritization and multiplexing enhancements | Nokia, Nokia Shanghai Bell |
| R1-2102868 | Discussion on intra-UE multiplexing and prioritization | China Telecom |
| R1-2102871 | Discussion on Intra-UE Multiplexing/Prioritization | Quectel, Langbo |
| R1-2102912 | Discussion on intra-UE multiplexing or prioritization | CMCC |
| R1-2102952 | Intra-UE Multiplexing and Prioritization | TCL Communication Ltd. |
| R1-2102984 | Intra-UE multiplexing prioritization for URLLC/IIoT | Xiaomi |
| R1-2103030 | Further analysis and details of intra-UE multiplexing and prioritization | Intel Corporation |
| R1-2103106 | Views on intra-UE multiplexing/prioritization | Apple |
| R1-2103166 | Intra-UE multiplexing and prioritization for IOT and URLLC | Qualcomm Incorporated |
| R1-2103207 | Discussion on Intra-UE multiplexing and prioritization of different priority | Panasonic Corporation |
| R1-2103239 | Uplink intra-UE multiplexing and prioritization | Samsung |
| R1-2103303 | Considerations on intra-UE UL multiplexing | Sony |
| R1-2103327 | Intra-UE Multiplexing/Prioritization | ETRI |
| R1-2103350 | Discussion on Intra-UE multiplexing/prioritization | LG Electronics |
| R1-2103475 | Enhancements on intra-UE UCI multiplexing with different priorities and channel prioritization | Sharp |
| R1-2103577 | Discussion on intra-UE multiplexing/prioritization for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2103613 | Intra-UE multiplexing enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2103632 | Discussion on intra-UE multiplexing | ITRI |
| R1-2103697 | Discussion on intra-UE multiplexing/prioritization for URLLC/IIoT | WILUS Inc. |
| R1-2103857 | Summary#1 of R17 intra-UE Multiplexing/Prioritization | Moderator (OPPO) |
| R1-2103868 | Summary#1 of email thread [104b-e-NR-R17-IIoT_URLLC-04] | Moderator (OPPO) |
| 8.3.4 | Other | |
| R1-2102396 | Enhancement for support of time synchronization | OPPO |
| R1-2102497 | Discussion on propagation delay compensation enhancements | ZTE |
| R1-2102525 | Discussion on propagation delay compensation enhancements | vivo |
| R1-2102632 | Discussion on propagation delay compensation enhancements | CATT |
| R1-2102698 | Discussion on propagation delay compensation for time synchronization | MediaTek Inc. |
| R1-2102748 | Propagation Delay Compensation Enhancements for Time Synchronization | Ericsson |
| R1-2102821 | Discussion on enhancements for propagation delay compensation | Nokia, Nokia Shanghai Bell |
| R1-2103031 | Further analysis and design considerations regarding propagation delay compensation | Intel Corporation |
| R1-2103167 | Enhancements for support of time synchronization for enhanced IIoT and URLLC | Qualcomm Incorporated |
| R1-2103240 | Discussion for propagation delay compensation enhancements | Samsung |
| R1-2103328 | Propagation delay compensation enhancements | ETRI |
| R1-2103351 | Discussion on propagation delay compensation enhancements | LG Electronics |
| R1-2103398 | Enhancements for support of time synchronization | Huawei, HiSilicon, SIA |
| R1-2103775 | Feature lead summary#1 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2103890 | Feature lead summary#2 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2103945 | Feature lead summary#3 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2104066 | Feature lead summary#4 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2104136 | Final feature lead summary on propagation delay compensation enhancements | Moderator (Huawei) |
| 8.4 | Solutions for NR to support non-terrestrial networks (NTN) | |
| R1-2102836 | NR_NTN_solutions work plan | THALES |
| R1-2103981 | Session notes for 8.4 (Solutions for NR to support non-terrestrial networks (NTN)) | Ad-Hoc Chair (Ericsson) |
| 8.4.1 | Timing relationship enhancements | |
| R1-2102341 | Discussion on timing relationship enhancements for NTN | Huawei, HiSilicon |
| R1-2102397 | Discussion on timing relationship enhancement | OPPO |
| R1-2102458 | Consideration on timing relationship enhancements | Spreadtrum Communications |
| R1-2102572 | Timing relationship enhancements to support NTN | CAICT |
| R1-2102633 | Timing relationship enhancement for NTN | CATT |
| R1-2102732 | Timing relationship enhancements in NTN | Asia Pacific Telecom, FGI, ITRI, III |
| R1-2102751 | Timing relationship enhancements for NR-NTN | MediaTek Inc. |
| R1-2102799 | Timing relationship enhancements for NTN | Zhejiang Lab |
| R1-2102864 | Discussion on Timing Relationship Enhancements in NR-NTN | China Telecom |
| R1-2102873 | Timing relationship for NTN | Panasonic Corporation |
| R1-2102884 | Discussion on timing relationship enhancements for NTN | CMCC |
| R1-2102914 | Discussion on timing relationship for NR-NTN | ZTE |
| R1-2102985 | Discussion on the timing relationship enhancement for NTN | Xiaomi |
| R1-2103032 | On timing relationship enhancements for NTN | Intel Corporation |
| R1-2103058 | On timing relationship enhancements for NTN | Ericsson |
| R1-2103107 | Discussion on Timing Relationship Enhancements in NTN | Apple |
| R1-2103168 | Enhancements on Timing Relationship for NTN | Qualcomm Incorporated |
| R1-2103241 | Timing relationship enhancements for NTN | Samsung |
| R1-2103276 | Timing relationship enhancement for NTN | InterDigital, Inc. |
| R1-2103304 | Calculation of timing relationship offsets | Sony |
| R1-2103532 | Discussion on NTN timing relationship | Lenovo, Motorola Mobility |
| R1-2103578 | Discussion on timing relationship enhancements for NTN | NTT DOCOMO, INC. |
| R1-2103619 | Discussions on timing relationship enhancements in NTN | LG Electronics |
| R1-2103633 | Timing relationship enhancements for NTN | ITRI |
| R1-2103656 | Discussion on Timing Relationship Enhancements for NTN | Fraunhofer IIS, Fraunhofer HHI |
| R1-2103669 | Discussion on time relations for NTN operation | Nokia, Nokia Shanghai Bell |
| R1-2103671 | Discussion on timing relationship enhancement in NTN | THALES |
| R1-2103776 | Feature lead summary#1 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2103874 | Feature lead summary#2 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2103914 | Feature lead summary#3 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2104026 | Feature lead summary#4 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2104099 | Feature lead summary#5 on timing relationship enhancements | Moderator (Ericsson) |
| 8.4.2 | Enhancements on UL time and frequency synchronization | |
| R1-2102342 | Discussion on UL time and frequency synchronization enhancement for NTN | Huawei, HiSilicon |
| R1-2102360 | Considerations on UL timing and frequency synchronization in NTN | THALES |
| R1-2102398 | Discussion on UL time and frequency synchronization | OPPO |
| R1-2102459 | Consideration on enhancements on UL time and frequency synchronization | Spreadtrum Communications |
| R1-2102555 | Discussion on UL time and frequency synchronization for NTN | PANASONIC R&D Center Germany |
| R1-2102573 | Considerations on Enhancements on UL Time Synchronization in NTN | CAICT |
| R1-2102634 | UL time and frequency compensation for NTN | CATT |
| R1-2102733 | UL time and frequency synchronization in NTN | Asia Pacific Telecom, FGI, ITRI, III |
| R1-2102752 | Enhancements on UL Time and Frequency Synchronisation for NR-NTN | MediaTek Inc. |
| R1-2102865 | Discussion on UL time and frequency synchronization for NR NTN | China Telecom |
| R1-2102885 | Enhancements on UL time and frequency synchronization for NTN | CMCC |
| R1-2102915 | Discussion on UL synchronization for NR-NTN | ZTE |
| R1-2102986 | Discussion on UL time and frequency synchronization for NTN | Xiaomi |
| R1-2103011 | UL time synchronization acquisition for NTN | Mitsubishi Electric RCE |
| R1-2103033 | On UL synchronization for NTN | Intel Corporation |
| R1-2103059 | On UL time and frequency synchronization enhancements for NTN | Ericsson |
| R1-2103108 | On Uplink Time and Frequency Synchronization for NTN | Apple |
| R1-2103169 | UL time and frequency synchronization for NTN | Qualcomm Incorporated |
| R1-2103242 | Enhancements on UL time and frequency synchronization for NTN | Samsung |
| R1-2103277 | UL time/frequency synchronization for NTN | InterDigital, Inc. |
| R1-2103305 | Enhancement for UL time synchronization | Sony |
| R1-2103533 | Discussion on NTN uplink time synchronization | Lenovo, Motorola Mobility |
| R1-2103544 | Discussions on doppler effect in time synchronization for NTN | BUPT |
| R1-2103579 | Discussion on UL time synchronization enhancements for NTN | NTT DOCOMO, INC. |
| R1-2103620 | Discussions on UL time and frequency synchronization enhancements in NTN | LG Electronics |
| R1-2103655 | Discussion on UL Time Synchronization for NTN | Fraunhofer IIS, Fraunhofer HHI |
| R1-2103670 | Discussion on time and frequency synchronization for NTN operation | Nokia, Nokia Shanghai Bell |
| R1-2103687 | On UL time and frequency synchronization enhancements for NR NTN | Sequans Communications |
| R1-2103731 | Further discussion on UL time synchronization methods for NTN systems | CEWiT, IITM, IITH |
| R1-2103792 | Feature lead summary #1 on enhancements on UL timing and frequency synchronization | Moderator (Thales) |
| R1-2103905 | Feature lead summary #2 on enhancements on UL timing and frequency synchronization | Moderator (Thales) |
| R1-2103989 | Feature lead summary #3 on enhancements on UL timing and frequency synchronization | Moderator (Thales) |
| R1-2103990 | Feature lead summary #4 on enhancements on UL timing and frequency synchronization | Moderator (Thales) |
| R1-2104076 | Feature lead summary #5 on enhancements on UL timing and frequency synchronization | Moderator (Thales) |
| 8.4.4 | Other (Void-not be handled during this e-meeting) | |
| R1-2102363 | Discussions on other aspects of NTN | BUPT |
| R1-2102477 | Discussions on other aspects of NTN | BUPT |
| R1-2103204 | Discussions on other aspects of NTN | BUPT |
| 8.5 | NR Positioning Enhancements | |
| R1-2103034 | Work Plan for NR Positioning Enhancements Work Item | Intel Corporation, CATT, Ericsson |
| R1-2103982 | Session notes for 8.5 (NR Positioning Enhancements) | Ad-Hoc Chair (Ericsson) |
| 8.5.1 | Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | |
| R1-2102348 | Enhancement to mitigate gNB and UE Rx/Tx timing error | Huawei, HiSilicon |
| R1-2102364 | Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | BUPT |
| R1-2102399 | Enhancement of timing-based positioning by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | OPPO |
| R1-2102526 | Discussion on potential enhancements for RX/TX timing delay mitigating | vivo |
| R1-2102635 | Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | CATT |
| R1-2102668 | Positioning accuracy improvement by mitigating timing delay | ZTE |
| R1-2102869 | Discussion on positioning enhancement by mitigating timing delays | China Telecom |
| R1-2102886 | Discussion on mitigation of gNB/UE Rx/Tx timing errors | CMCC |
| R1-2103002 | Views on mitigating UE and gNB Rx/Tx timing errors | Nokia, Nokia Shanghai Bell |
| R1-2103005 | Discussion on accuracy improvements by mitigating timing delays | InterDigital, Inc. |
| R1-2103035 | Mitigation of UE Rx/Tx and gNB Rx/Tx timing errors | Intel Corporation |
| R1-2103109 | Positioning accuracy enhancements under timing errors | Apple |
| R1-2103170 | Enhancements on Timing Error Mitigations for improved Accuracy | Qualcomm Incorporated |
| R1-2103243 | Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Samsung |
| R1-2103306 | Discussion on mitigating UE Rx/Tx and gNB Rx/Tx timing delays | Sony |
| R1-2103372 | Enhancements for mitigation of Tx/Rx Delays | Lenovo, Motorola Mobility |
| R1-2103580 | Discussion on mitigating UE and gNB Rx/Tx timing delays | NTT DOCOMO, INC. |
| R1-2103600 | Mitigation of RX/TX timing delays for higher accuracy | MediaTek Inc. |
| R1-2103621 | Discussion on accuracy improvement by mitigating UE Rx/Tx and gNB Rx/Tx timing delays | LG Electronics |
| R1-2103681 | On methods for Rx/Tx timing delays mitigation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2103682 | Discussion on mitigation of Tx-Rx timing delays | CEWiT, IITM, IITH |
| R1-2103735 | Techniques mitigating Rx/Tx timing delays | Ericsson |
| R1-2103771 | Techniques mitigating Rx/Tx timing delays | Ericsson |
| R1-2103781 | FL Summary for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2103875 | FL Summary#2 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2103903 | FL Summary#3 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2103992 | FL Summary#4 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2104053 | [DRAFT] LS on UE/TRP Tx/Rx Timing Errors | CATT |
| R1-2104111 | LS on UE/TRP Tx/Rx Timing Errors | RAN1, CATT |
| 8.5.2 | Accuracy improvements for UL-AoA positioning solutions | |
| R1-2102400 | Enhancements for UL AoA Positioning | OPPO |
| R1-2102527 | Discussion on potential enhancements for UL-AoA method | vivo |
| R1-2102636 | Discussion on accuracy improvements for UL-AoA positioning solutions | CATT |
| R1-2102669 | Accuracy improvement for UL-AoA positioning solutions | ZTE |
| R1-2102784 | Accuracy Improvement of UL-AoA Positioning | FUTUREWEI |
| R1-2102887 | Discussion on UL-AoA enhancements | CMCC |
| R1-2103003 | Views on enhancing UL AoA | Nokia, Nokia Shanghai Bell |
| R1-2103006 | Discussion on UL-AoA positioning solutions | InterDigital, Inc. |
| R1-2103036 | Enhancements of UL-AoA positioning solution | Intel Corporation |
| R1-2103110 | Accuracy enhancements for UL-AoA positioning technique | Apple |
| R1-2103171 | Potential Enhancements on UL-AOA positioning | Qualcomm Incorporated |
| R1-2103244 | Accuracy improvements for UL-AoA positioning solutions | Samsung |
| R1-2103307 | Discussion on accuracy improvements for UL-AoA positioning method | Sony |
| R1-2103400 | Enhancement for UL AoA positioning | Huawei, HiSilicon |
| R1-2103581 | Discussion on UL-AoA positioning enhancements | NTT DOCOMO, INC. |
| R1-2103622 | Discussion on accuracy improvement for UL-AoA positioning | LG Electronics |
| R1-2103683 | UL-AoA positioning enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2103684 | Discussion on potential enhancements for UL AoA positioning | CEWiT, IITM, IITH |
| R1-2103736 | Enhancements of UL-AoA positioning solutions | Ericsson |
| R1-2103794 | Feature Lead Summary #0 on Enhancements of UL-AOA Positioning | Moderator (Intel Corporation) |
| R1-2103862 | Feature Lead Summary #1 on Enhancements of UL-AOA Positioning | Moderator (Intel Corporation) |
| R1-2103863 | Feature Lead Summary #2 on Enhancements of UL-AOA Positioning | Moderator (Intel Corporation) |
| 8.5.3 | Accuracy improvements for DL-AoD positioning solutions | |
| R1-2102401 | Enhancements for DL-AoD positioning | OPPO |
| R1-2102528 | Discussion on potential enhancements for DL-AoD method | vivo |
| R1-2102574 | Discussion on enhancements for DL-AoD positioning | CAICT |
| R1-2102637 | Discussion on accuracy improvements for DL-AoD positioning solutions | CATT |
| R1-2102670 | Accuracy improvements for DL-AoD positioning solutions | ZTE |
| R1-2102785 | Accuracy Improvement of DL-AoD Positioning | FUTUREWEI |
| R1-2102870 | Disscussion on accuracy improvements for DL-AoD positioning method | China Telecom |
| R1-2102888 | Discussion on DL-AoD enhancements | CMCC |
| R1-2102987 | Accuracy improvements for DL-AoD positioning solutions | Xiaomi |
| R1-2103004 | Views on enhancing DL AoD | Nokia, Nokia Shanghai Bell |
| R1-2103007 | Discussion on DL-AoD positioning solutions | InterDigital, Inc. |
| R1-2103037 | Enhancements of DL-AoD positioning solution | Intel Corporation |
| R1-2103111 | Accuracy enhancements for DL-AoD positioning technique | Apple |
| R1-2103172 | Potential Enhancements on DL-AoD positioning | Qualcomm Incorporated |
| R1-2103245 | Accuracy improvements for DL-AoD positioning solutions | Samsung |
| R1-2103308 | Discussion on accuracy improvements for DL-AoD positioning method | Sony |
| R1-2103373 | DL-AoD Positioning Enhancements | Lenovo, Motorola Mobility |
| R1-2103401 | Enhancement for DL AoD positioning | Huawei, HiSilicon |
| R1-2103582 | Discussion on DL-AoD positioning enhancements | NTT DOCOMO, INC. |
| R1-2103623 | Discussion on accuracy improvement for DL-AoD positioning | LG Electronics |
| R1-2103649 | Accuracy enhancement for DL-AOD technique | MediaTek Inc. |
| R1-2103685 | DL-AoD positioning enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2103686 | Discussion on potential enhancements for DL-AoD positioning | CEWiT, IITM, IITH |
| R1-2103737 | Enhancements of DL-AoD positioning solutions | Ericsson |
| R1-2103865 | FL summary #1 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2103951 | FL summary #2 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2104047 | FL summary #3 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2104088 | [DRAFT] LS on DL-AoD angle calculation enhancement | Ericsson |
| R1-2104089 | LS on DL-AoD angle calculation enhancement | RAN1, Ericsson |
| 8.5.6 | Other (Void-not be handled during this e-meeting) | |
| R1-2102802 | Carrier Phase Based Positioning for NR | DanKook University |
| 8.6 | Support of Reduced Capability NR Devices | |
| R1-2102721 | WI work plan for RedCap | Rapporteur (Ericsson) |
| R1-2104027 | RAN1 agreements for Rel-17 NR RedCap | Rapporteur (Ericsson) |
| 8.6.1 | UE complexity reduction | |
| R1-2102866 | Discussion on UE complexity reduction for RedCap | China Telecom |
| R1-2103173 | Complexity Reduction for RedCap Devices | Qualcomm Incorporated |
| 8.6.1.1 | Aspects related to reduced maximum UE bandwidth | |
| R1-2102311 | Discussion on reduced maximum UE bandwidth for RedCap | Huawei, HiSilicon |
| R1-2102402 | Discussion on reduced UE bandwidth | OPPO |
| R1-2102460 | Discussion on aspects related to reduced maximum UE bandwidth | Spreadtrum Communications |
| R1-2102529 | Discussion on reduced maximum UE bandwidth | vivo, Guangdong Genius |
| R1-2102638 | Discussion on reduced maximum UE bandwidth | CATT |
| R1-2102649 | UE complexity reduction aspects related to reduced maximum UE bandwidth | Nokia, Nokia Shanghai Bell |
| R1-2102672 | Reduced maximum UE bandwidth for RedCap | TCL Communication Ltd. |
| R1-2102699 | On reduced maximum bandwidth for RedCap UEs | MediaTek Inc. |
| R1-2102722 | Reduced maximum UE bandwidth for RedCap | Ericsson |
| R1-2102734 | Discussion on reduced maximum UE bandwidth | Asia Pacific Telecom, FGI |
| R1-2102778 | Bandwidth reduction for RedCap UEs | FUTUREWEI |
| R1-2102854 | Bandwidth reduction for reduced capability NR devices | ZTE |
| R1-2102889 | Discussion on reduced maximum UE bandwidth | CMCC |
| R1-2102988 | Discussion on the reduced maximum UE bandwidth for RedCap | Xiaomi |
| R1-2103038 | On reduced BW support for RedCap devices | Intel Corporation |
| R1-2103112 | On reduced maximum UE bandwidth for Redcap | Apple |
| R1-2103174 | BW Reduction for RedCap UE | Qualcomm Incorporated |
| R1-2103246 | Discussion on bandwidth reduction for RedCap UEs. | Samsung |
| R1-2103352 | Aspects related to the reduced maximum UE bandwidth of RedCap | LG Electronics |
| R1-2103421 | Reduced maximum bandwidth for RedCap UEs | InterDigital, Inc. |
| R1-2103455 | Discussion on BWP | NEC |
| R1-2103476 | Discussion on reduced maximum UE bandwidth | Sharp |
| R1-2103534 | Reduced maximum UE bandwidth for RedCap | Lenovo, Motorola Mobility |
| R1-2103540 | Aspects related to reduced maximum UE bandwidth | Panasonic Corporation |
| R1-2103583 | Discussion on reduced maximum UE bandwidth for RedCap | NTT DOCOMO, INC. |
| R1-2103650 | On aspects related to reduced maximum UE BW | Nordic Semiconductor ASA |
| R1-2103664 | Discussion on aspects related to reduced maximum UE bandwidth | ASUSTeK |
| R1-2103698 | Discussion on reduced maximum UE bandwidth for RedCap UE | WILUS Inc. |
| R1-2103767 | Reduced maximum UE bandwidth for RedCap | Lenovo, Motorola Mobility |
| R1-2103823 | FL summary #1 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2103824 | FL summary #2 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2103825 | FL summary #3 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2103944 | FL summary #4 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2104046 | Draft LS on RF switching time for RedCap UE | Ericsson |
| 8.6.1.2 | Aspects related to reduced number of Rx branches | |
| R1-2102355 | Discussion on reduced number of Rx branches for RedCap | Huawei, HiSilicon |
| R1-2102403 | Discussion on reduced number of UE Rx branches | OPPO |
| R1-2102461 | Discussion on aspects related to reduced number of Rx branches | Spreadtrum Communications |
| R1-2102530 | Discussion on reduced number of Rx branches | vivo, Guangdong Genius |
| R1-2102639 | Discussion on reduced number of Rx branches | CATT |
| R1-2102650 | UE complexity reduction aspects related to reduced number of Rx branches | Nokia, Nokia Shanghai Bell |
| R1-2102700 | On reduced number of Rx branches for RedCap UEs | MediaTek Inc. |
| R1-2102723 | Reduced number of Rx branches for RedCap | Ericsson |
| R1-2102779 | RX branch reduction for RedCap UEs | FUTUREWEI |
| R1-2102855 | Discussion on reduced number of UE Rx branches | ZTE |
| R1-2102890 | Discussion on reduced number of Rx branches | CMCC |
| R1-2102989 | Aspects on reduced number of Rx branches | Xiaomi |
| R1-2103039 | On reduced number of Rx branches for RedCap devices | Intel Corporation |
| R1-2103113 | On reduced number of Rx branches for Redcap | Apple |
| R1-2103175 | RX Branch Reduction for RedCap UE | Qualcomm Incorporated |
| R1-2103247 | Discussion on reduced number of RX branches for RedCap UEs | Samsung |
| R1-2103353 | Aspects related to the reduced number of Rx branches of RedCap | LG Electronics |
| R1-2103404 | Discussion on solutions for reducing PDCCH blocking | CEWiT |
| R1-2103422 | Reduced number of Rx branches for RedCap UEs | InterDigital, Inc. |
| R1-2103456 | Discussion on aspects of coverage recovery | NEC |
| R1-2103477 | Discussion on reduced minimum number of Rx branches | Sharp |
| R1-2103535 | Reduced number or Rx branches for RedCap | Lenovo, Motorola Mobility |
| R1-2103541 | Aspects related to reduced number of Rx branches | Panasonic Corporation |
| R1-2103584 | Discussion on reduced minimum number of Rx branches for RedCap | NTT DOCOMO, INC. |
| R1-2103651 | On aspects related to reduced number of Rx branches | Nordic Semiconductor ASA |
| R1-2103665 | Discussion on aspects related to reduced number of Rx branches | ASUSTeK |
| R1-2103799 | FL summary #1 for reduced number of Rx branches for RedCap | Moderator (Apple) |
| R1-2103866 | FL summary #2 for reduced number of Rx branches for RedCap | Moderator (Apple) |
| R1-2103899 | FL summary #3 for reduced number of Rx branches for RedCap | Moderator (Apple) |
| R1-2103967 | FL summary #4 for reduced number of Rx branches for RedCap | Moderator (Apple) |
| 8.6.1.3 | Aspects related to duplex operation | |
| R1-2102356 | Discussion on duplex operation for RedCap | Huawei, HiSilicon |
| R1-2102404 | On half-duplex operation | OPPO |
| R1-2102462 | Discussion on aspects related to duplex operation | Spreadtrum Communications |
| R1-2102531 | Discussion on RedCap half-duplex operation | vivo, Guangdong Genius |
| R1-2102640 | Discussion on HD-FDD operation | CATT |
| R1-2102651 | UE complexity reduction aspects related to duplex operation | Nokia, Nokia Shanghai Bell |
| R1-2102701 | On half duplex operation for RedCap UEs | MediaTek Inc. |
| R1-2102724 | Duplex operation for RedCap | Ericsson |
| R1-2102735 | Discussion on aspects related to duplex operation | Asia Pacific Telecom, FGI |
| R1-2102856 | HD-FDD for reduced capability NR devices | ZTE |
| R1-2102874 | Discussion on aspects related to duplex operation | Potevio Company Limited |
| R1-2102891 | Discussion on collision handling of HD-FDD operation | CMCC |
| R1-2102990 | Discussion on Half-duplex FDD operation of Redcap UE | Xiaomi |
| R1-2103040 | On HD-FDD support for RedCap devices | Intel Corporation |
| R1-2103114 | On aspects related to half-duplex operation | Apple |
| R1-2103176 | Type-A HD-FDD for RedCap UE | Qualcomm Incorporated |
| R1-2103248 | HD-FDD Operation for RedCap UEs | Samsung |
| R1-2103309 | Half-duplex FDD operation for Redcap UEs | Sony |
| R1-2103354 | Aspects related to the duplex operation of RedCap | LG Electronics |
| R1-2103423 | Duplex operation for RedCap UEs | InterDigital, Inc. |
| R1-2103478 | Discussion on the duplex operation of redcap UEs | Sharp |
| R1-2103536 | Half duplex operation for RedCap | Lenovo, Motorola Mobility |
| R1-2103542 | Aspects related to duplex operation | Panasonic Corporation |
| R1-2103585 | Discussion on duplex operation for RedCap | NTT DOCOMO, INC. |
| R1-2103652 | On aspects related to duplex operation | Nordic Semiconductor ASA |
| R1-2103666 | Discussion on aspects related to duplex operation | ASUSTeK |
| R1-2103699 | Discussion on duplex operation for RedCap UE | WILUS Inc. |
| R1-2103796 | FL summary #1 on duplex operation for RedCap | Moderator (Qualcomm Inc.) |
| R1-2103884 | FL summary #2 on duplex operation for RedCap | Moderator (Qualcomm Inc.) |
| R1-2103935 | FL summary #3 on duplex operation for RedCap | Moderator (Qualcomm Inc.) |
| 8.6.3 | Other (Void-not be handled during this e-meeting) | |
| R1-2102801 | Other aspects of RedCap | TCL Communication Ltd. |
| 8.7.1.1 | Potential paging enhancements | |
| R1-2102316 | Paging enhancements for UE power saving in IDLE/inactive mode | Huawei, HiSilicon |
| R1-2102405 | Further discussion on Paging enhancements for power saving | OPPO |
| R1-2102463 | Discussion on potential paging enhancements | Spreadtrum Communications |
| R1-2102532 | Paging enhancements for idle/inactive mode UE power saving | vivo |
| R1-2102565 | Discussion on power saving enhancements for paging | ZTE,Sanechips |
| R1-2102641 | Paging enhancement for UE power saving | CATT |
| R1-2102681 | On paging enhancements for idle/inactive mode UE power saving | MediaTek Inc. |
| R1-2102805 | On paging enhancement | Panasonic |
| R1-2102892 | Discussion on paging early indication design | CMCC |
| R1-2102991 | Paging enhancement for power saving | Xiaomi |
| R1-2103041 | On Paging Enhancements for UE Power Saving | Intel Corporation |
| R1-2103115 | Paging early indication for idle/inactive-mode UE | Apple |
| R1-2103177 | Paging enhancements for idle/inactive UE power saving | Qualcomm Incorporated |
| R1-2103249 | Discussion on paging enhancements | Samsung |
| R1-2103310 | Discussion on potential paging enhancements | Sony |
| R1-2103355 | Discussion on potential paging enhancements | LG Electronics |
| R1-2103405 | On paging enhancements for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2103424 | Paging enhancements for UE power saving | InterDigital, Inc. |
| R1-2103586 | Discussion on paging enhancements | NTT DOCOMO, INC. |
| R1-2103614 | Paging enhancement for UE power saving | Lenovo, Motorola Mobility |
| R1-2103642 | Design of Paging Enhancements | Ericsson |
| R1-2103653 | On paging early indication | Nordic Semiconductor ASA |
| R1-2103768 | Paging enhancement for power saving | Xiaomi |
| R1-2103848 | Summary of paging enhancements | Moderator (MediaTek) |
| 8.7.1.2 | TRS/CSI-RS occasion(s) for idle/inactive UEs | |
| R1-2102317 | Assistance RS occasions for IDLE/inactive mode | Huawei, HiSilicon |
| R1-2102406 | Further discussion on RS occasion for idle/inactive UEs | OPPO |
| R1-2102464 | Consideration on TRS/CSI-RS occasion(s) for idle/inactive UEs | Spreadtrum Communications |
| R1-2102478 | TRS/CSI-RS occasions for idle/inactive UE | TCL Communication Ltd. |
| R1-2102533 | TRS/CSI-RS occasion(s) for idle/inactive UEs | vivo |
| R1-2102566 | TRS for RRC idle and inactive UEs | ZTE,Sanechips |
| R1-2102642 | Configuration of TRS/CSI-RS for paging enhancement | CATT |
| R1-2102682 | On TRS/CSI-RS occasion(s) for idle/inactive mode UE power saving | MediaTek Inc. |
| R1-2102806 | Potential enhancements for TRS/CSI-RS occasion(s) for idle/inactive UEs | Panasonic |
| R1-2102893 | Discussion on TRS/CSI-RS occasion(s) for IDLE/INACTIVE-mode UEs | CMCC |
| R1-2102992 | On TRS/CSI-RS configuration and indication for idle/inactive UEs | Xiaomi |
| R1-2103042 | TRS/CSI-RS functionality during idle/inactive mode | Intel Corporation |
| R1-2103116 | Indication of TRS/CSI-RS for idle/inactive-mode UE power saving | Apple |
| R1-2103178 | TRS/CSI-RS for idle/inactive UE power saving | Qualcomm Incorporated |
| R1-2103250 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | Samsung |
| R1-2103251 | Moderator summary for TRS/CSI-RS occasion(s) for idle/inactive Ues | Moderator (Samsung) |
| R1-2103311 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | Sony |
| R1-2103356 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | LG Electronics |
| R1-2103406 | On RS information to IDLE/Inactive mode Ues | Nokia, Nokia Shanghai Bell |
| R1-2103425 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | InterDigital, Inc. |
| R1-2103479 | On TRS/CSI-RS occasions for idle/inactive UEs | Sharp |
| R1-2103587 | Discussion on TRS/CSI-RS occasion for idle/inactive Ues | NTT DOCOMO, INC. |
| R1-2103615 | Provision of TRS/CSI-RS for idle/inactive UEs | Lenovo, Motorola Mobility |
| R1-2103643 | Provisioning of TRS occasions to Idle/Inactive UEs | Ericsson |
| R1-2103654 | On TRS design for idle/inactive UEs | Nordic Semiconductor ASA |
| R1-2104115 | Final summary for TRS/CSI-RS occasion(s) for idle/inactive Ues | Moderator (Samsung) |
| 8.7.1.3 | Other | |
| R1-2102407 | Paging and TRS indication in idle/inactive modes | OPPO |
| R1-2102534 | Discussion on paging grouping | vivo |
| R1-2102567 | Additional simulation results of UE power consumption in RRC idle and inactive state | ZTE,Sanechips |
| R1-2102643 | Details of PEI configuration | CATT |
| R1-2103389 | Analysis on power consumption for IDLE mode and RedCap | Huawei, HiSilicon |
| R1-2103426 | Paging indication based on sub-time units | InterDigital, Inc. |
| R1-2103644 | Modeling of Network Power Consumption | Ericsson |
| 8.7.2 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime (Void-not be handled during this e-meeting) | |
| R1-2103634 | Discussion on DCI-based power saving adaptation | ITRI |
| 8.8.1.1 | Enhancements on PUSCH repetition type A (Void-not be handled during this e-meeting) | |
| R1-2102673 | Discussion on PUSCH TB processing over multiple slots | TCL Communication Ltd. |
| R1-2103459 | Design considerations for PUSCH repetition Type A Enhancements | Sierra Wireless, S.A. |
| 8.8.1.2 | TB processing over multi-slot PUSCH | |
| R1-2102314 | Discussion on TB processing over multi-slot PUSCH | Huawei, HiSilicon |
| R1-2102408 | Issues for TB over multi-slot PUSCH | OPPO |
| R1-2102498 | Discussion on TB processing over multi-slot PUSCH | ZTE |
| R1-2102535 | Discussion on PUSCH TB processing over multiple slots | vivo |
| R1-2102644 | Discussion on TB processing over multi-slot PUSCH | CATT |
| R1-2102691 | Discussion on TB processing over multi-slot PUSCH | MediaTek Inc. |
| R1-2102718 | Views on TB processing over multi-slot PUSCH | Fujitsu |
| R1-2102861 | Discussion on TB processing over multi-slot PUSCH | China Telecom |
| R1-2102894 | Discussion on TB processing over multi-slot PUSCH | CMCC |
| R1-2102913 | On TB processing over multiple slots for PUSCH | Indian Institute of Tech (H) |
| R1-2102993 | TB processing over multi-slot PUSCH | Xiaomi |
| R1-2103008 | TB processing over multi-slot PUSCH | InterDigital, Inc. |
| R1-2103043 | Discussion on TB processing over multi-slot PUSCH | Intel Corporation |
| R1-2103117 | Discussion on TB processing over multi-slot PUSCH | Apple |
| R1-2103179 | TB processing over multi-slot PUSCH | Qualcomm Incorporated |
| R1-2103208 | Discussion on TB processing over multi-slot PUSCH | Panasonic Corporation |
| R1-2103252 | TB processing over multi-slot PUSCH | Samsung |
| R1-2103381 | Transport block processing for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2103445 | TB Processing over Multi-Slot PUSCH | Ericsson |
| R1-2103461 | Design Considerations for TB Processing over Multi-Slot PUSCH | Sierra Wireless, S.A. |
| R1-2103480 | TB processing over multi-slot PUSCH | Sharp |
| R1-2103514 | Discussion on TB processing over multi-slot PUSCH | NEC |
| R1-2103588 | TB processing over multi-slot PUSCH | NTT DOCOMO, INC. |
| R1-2103616 | Enhancements for TB processing over multi-slot PUSCH | Lenovo, Motorola Mobility |
| R1-2103625 | Discussions on TB processing over multi-slot PUSCH | LG Electronics |
| R1-2103700 | Discussion on TB processing over multi-slot PUSCH | WILUS Inc. |
| R1-2103876 | FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia) |
| R1-2104102 | FL final summary of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia) |
| 8.8.1.3 | Joint channel estimation for PUSCH | |
| R1-2102313 | Discussion on Joint channel estimation for PUSCH | Huawei, HiSilicon |
| R1-2102409 | Consideration on Joint channel estimation for PUSCH | OPPO |
| R1-2102465 | Consideration on joint channel estimation over multi-PUSCH | Spreadtrum Communications |
| R1-2102499 | Discussion on joint channel estimation for PUSCH | ZTE |
| R1-2102536 | Discussion on Joint channel estimation for PUSCH | vivo |
| R1-2102645 | Discussion on joint channel estimation for PUSCH | CATT |
| R1-2102692 | Discussion on joint channel estimation for PUSCH | MediaTek Inc. |
| R1-2102862 | Discussion on joint channel estimation for PUSCH | China Telecom |
| R1-2102895 | Discussion on joint channel estimation for PUSCH | CMCC |
| R1-2102994 | Joint channel estimation for PUSCH | Xiaomi |
| R1-2103009 | Discussions on joint channel estimation for PUSCH | InterDigital, Inc. |
| R1-2103044 | Discussion on joint channel estimation for PUSCH | Intel Corporation |
| R1-2103118 | Discussion on joint channel estimation for PUSCH | Apple |
| R1-2103180 | Joint channel estimation for PUSCH | Qualcomm Incorporated |
| R1-2103253 | Joint channel estimation for PUSCH | Samsung |
| R1-2103312 | UE configuration for enhanced JCE in TDD | Sony |
| R1-2103382 | Joint channel estimation for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2103446 | Joint Channel Estimation for PUSCH | Ericsson |
| R1-2103458 | Discussion on joint channel estimation for PUSCH | Panasonic Corporation |
| R1-2103460 | Design Considerations for Joint channel estimation for PUSCH | Sierra Wireless, S.A. |
| R1-2103481 | Joint channel estimation for multi-slot PUSCH | Sharp |
| R1-2103589 | Joint channel estimation for PUSCH | NTT DOCOMO, INC. |
| R1-2103617 | Enhancements for joint channel estimation for multiple PUSCH | Lenovo, Motorola Mobility |
| R1-2103626 | Discussions on joint channel estimation for PUSCH | LG Electronics |
| R1-2103701 | Discussion on joint channel estimation for PUSCH | WILUS Inc. |
| R1-2103808 | FL Summary of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2104006 | [104b-e-NR-R17-CovEnh-02] Summary of email discussion on joint channel estimation for PUSCH | Moderator (China Telecom) |
| 8.8.3 | Type A PUSCH repetitions for Msg3 | |
| R1-2102315 | Discussion on Msg3 repetition for coverage enhancement | Huawei, HiSilicon |
| R1-2102410 | Type A PUSCH repetitions for Msg3 coverage | OPPO |
| R1-2102466 | Discussion on type A PUSCH repetitions for Msg3 | Spreadtrum Communications |
| R1-2102500 | Discussion on support of Type A PUSCH repetitions for Msg3 | ZTE |
| R1-2102537 | Discussion on Type A PUSCH repetitions for Msg3 | vivo |
| R1-2102646 | Discussion on Type A PUSCH repetitions for Msg3 | CATT |
| R1-2102863 | Discussion on type A PUSCH repetitions for Msg3 | China Telecom |
| R1-2102896 | Discussion on type A PUSCH repetitions for Msg3 | CMCC |
| R1-2102995 | Type A PUSCH repetition for Msg3 | Xiaomi |
| R1-2103010 | Type A PUSCH repetitions for Msg3 | InterDigital, Inc. |
| R1-2103045 | On Msg3 PUSCH repetition | Intel Corporation |
| R1-2103119 | Discussion on Msg3 Coverage Enhancement | Apple |
| R1-2103181 | Type A PUSCH repetition for Msg3 | Qualcomm Incorporated |
| R1-2103209 | Discussion on Type A PUSCH repetitions for Msg.3 | Panasonic Corporation |
| R1-2103254 | Type A PUSCH repetitions for Msg3 | Samsung |
| R1-2103329 | Type A PUSCH repetitions for Msg3 | ETRI |
| R1-2103383 | Approaches and solutions for Type A PUSCH repetitions for Msg3 | Nokia, Nokia Shanghai Bell |
| R1-2103447 | Type A PUSCH Repetition for Msg3 | Ericsson |
| R1-2103482 | Type A repetition for msg3 PUSCH | Sharp |
| R1-2103515 | Discussion on PUSCH repetitions for Msg3 | NEC |
| R1-2103590 | Type A PUSCH repetitions for Msg3 | NTT DOCOMO, INC. |
| R1-2103618 | Type A PUSCH repetition for Msg3 | Lenovo, Motorola Mobility |
| R1-2103627 | Discussion on coverage enhancement for Msg3 PUSCH | LG Electronics |
| R1-2103702 | Discussion on Type A PUSCH repetitions for Msg3 | WILUS Inc. |
| R1-2103772 | Discussion on type A PUSCH repetitions for Msg3 | CMCC |
| R1-2103829 | Feature lead summary #1 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2104101 | Feature lead summary #2 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| 8.9 | Rel-17 enhancements for NB-IoT and LTE-MTC | |
| R1-2103763 | Work plan of Rel-17 enhancements for NB-IoT and LTE-MTC | Huawei, Ericsson |
| R1-2103983 | Session notes for 8.9 (Rel-17 enhancements for NB-IoT and LTE-MTC) | Ad-hoc Chair (Samsung) |
| 8.9.1 | Support of 16-QAM for unicast in UL and DL for NB-IoT | |
| R1-2102357 | Support of 16QAM for unicast in UL and DL in NB-IoT | Huawei, HiSilicon |
| R1-2102652 | Support of 16-QAM for NB-IoT | Nokia, Nokia Shanghai Bell |
| R1-2102680 | Switching point between QPSK and 16QAM and DCI design for 16QAM in R17 | MediaTek Inc. |
| R1-2102857 | Discussion on UL and DL 16QAM for NB-IoT | ZTE |
| R1-2103067 | Support of 16-QAM for NB-IoT | Qualcomm Incorporated |
| R1-2103531 | Support 16QAM for NBIoT | Lenovo, Motorola Mobility |
| R1-2103723 | Support of 16-QAM for unicast in UL and DL in NB-IoT | Ericsson |
| R1-2103853 | Feature lead summary #1 on 104b-e-LTE-Rel17_NB_IoT_eMTC-01 | Moderator (Huawei) |
| R1-2103954 | Feature lead summary #2 on 104b-e-LTE-Rel17_NB_IoT_eMTC-01 | Moderator (Huawei) |
| 8.9.2 | Support additional PDSCH scheduling delay for introduction of 14-HARQ processes in DL for eMTC | |
| R1-2102358 | Support of 14-HARQ processes in DL for HD-FDD MTC UEs | Huawei, HiSilicon |
| R1-2102653 | Support of 14-HARQ processes in DL for eMTC | Nokia, Nokia Shanghai Bell |
| R1-2102858 | Remaining issues on 14-HARQ processes in DL for eMTC | ZTE |
| R1-2103068 | Support of 14 HARQ processes and scheduling delay | Qualcomm Incorporated |
| R1-2103464 | Design considerations to support 14-HARQ Feature for LTE-M | Sierra Wireless, S.A. |
| R1-2103724 | Support of 14 HARQ processes in DL in LTE-MTC | Ericsson |
| R1-2103859 | Feature Lead Summary [104b-e-LTE-Rel17_NB_IoT_eMTC-02]: 1st check point | Moderator (Ericsson) |
| R1-2103860 | Feature Lead Summary [104b-e-LTE-Rel17_NB_IoT_eMTC-02]: 2nd check point | Moderator (Ericsson) |
| R1-2103861 | Feature Lead Summary [104b-e-LTE-Rel17_NB_IoT_eMTC-02]: final | Moderator (Ericsson) |
| 8.9.3 | Support a maximum DL TBS of 1736 bits as a Rel-17 optional UE capability | |
| R1-2102359 | Support of a max DL TBS of 1736 bits in LTE-MTC | Huawei, HiSilicon |
| R1-2102654 | Support of a maximum DL TBS of 1736 bits for eMTC | Nokia, Nokia Shanghai Bell |
| R1-2102859 | Remaining issues on DL TBS increase for eMTC | ZTE |
| R1-2103069 | Support of larger TBS for eMTC | Qualcomm Incorporated |
| R1-2103313 | Remaining issues for support of DL TBS of 1736 bits for eMTC | Sony |
| R1-2103462 | Design considerations to support DL TBS of 1736 bits for LTE-M | Sierra Wireless, S.A. |
| R1-2103725 | Support of a maximum DL TBS of 1736 bits in LTE-MTC | Ericsson |
| R1-2103942 | LS on Agreements Related to Support of a maximum DL TBS of 1736 bits as a Rel-17 optional UE capability | RAN1, Sony |
| R1-2104086 | Feature Lead Summary [104b-e-LTE-Rel17_NB_IoT_eMTC-03] | Moderator (Sony) |
| R1-2104087 | Summary of NWM discussion for [104b-e-LTE-Rel17_NB_IoT_eMTC-03] | Moderator (Sony) |
| 8.10 | Enhancements to Integrated Access and Backhaul | |
| R1-2103182 | Workplan for Rel-17 IAB | Qualcomm Incorporated |
| R1-2103984 | Session notes for 8.10 (Enhancements to Integrated Access and Backhaul) | Ad-hoc Chair (Samsung) |
| 8.10.1 | Enhancements to resource multiplexing between child and parent links of an IAB node | |
| R1-2102340 | Resource multiplexing between backhaul and access for IAB duplexing enhancements | Huawei, HiSilicon |
| R1-2102538 | Enhancement to resource multiplexing between child and parent links | vivo |
| R1-2103046 | Enhancements to Resource Multiplexing between Child and Parent Links of an IAB Node | Intel Corporation |
| R1-2103120 | Enhanced resource multiplexing within an IAB node | Apple |
| R1-2103183 | Resource management for enhanced duplexing | Qualcomm Incorporated |
| R1-2103255 | Enhancements to Resource Multiplexing for NR IAB | Samsung |
| R1-2103330 | Discussion on IAB resource multiplexing enhancements | ETRI |
| R1-2103374 | Discussions on enhancements to resource multiplexing between child and parent links of an IAB node | CEWiT |
| R1-2103435 | Enhancements for resource multiplexing among IAB backhaul and access links | Nokia, Nokia Shanghai Bell |
| R1-2103436 | Enhancements for IAB resource multiplexing | AT&T |
| R1-2103497 | Enhancements to the IAB resource multiplexing | ZTE, Sanechips |
| R1-2103591 | Resource multiplexing between child and parent links of an IAB node | NTT DOCOMO, INC. |
| R1-2103608 | Resource multiplexing in enhanced IAB systems | Lenovo, Motorola Mobility |
| R1-2103629 | Discussions on IAB resource multiplexing enhancements | LG Electronics |
| R1-2103712 | Resource multiplexing and DC in enhanced IAB | Ericsson |
| R1-2103837 | Summary of [104b-e-NR-eIAB-01] – Kickoff | Moderator (AT&T) |
| R1-2103838 | Summary of [104b-e-NR-eIAB-01] – 1stCheckpoint | Moderator (AT&T) |
| R1-2103839 | Summary of [104b-e-NR-eIAB-01] – 2nd Checkpoint | Moderator (AT&T) |
| R1-2103958 | Summary of [104b-e-NR-eIAB-01] – Final Checkpoint | Moderator (AT&T) |
| 8.10.2 | Other enhancements for simultaneous operation of IAB-node’s child and parent links (Void-not be handled during this e-meeting) | |
| R1-2103047 | Other Enhancements for Simultaneous Operations | Intel Corporation |
| 8.11.1 | Resource allocation enhancement | |
| R1-2103256 | On Resource Allocation Enhacements | Samsung |
| 8.11.1.1 | Resource allocation for power saving | |
| R1-2102323 | Sidelink resource allocation to reduce power consumption | Huawei, HiSilicon |
| R1-2102361 | Sidelink resource allocation for power saving | Nokia, Nokia Shanghai Bell |
| R1-2102411 | Power saving mechanism in NR sidelink | OPPO |
| R1-2102467 | Discussion on sidelink resource allocation for power saving | Spreadtrum Communications |
| R1-2102539 | Resource allocation for sidelink power saving | vivo |
| R1-2102575 | Considerations on partial sensing in NR V2X | CAICT |
| R1-2102606 | Discussion on resource allocation for power saving | CATT, GOHIGH |
| R1-2102708 | Discussion on sidelink power saving | MediaTek Inc. |
| R1-2102719 | Considerations on partial sensing and DRX in NR sidelink | Fujitsu |
| R1-2102780 | Power consumption reduction for sidelink resource allocation | FUTUREWEI |
| R1-2102797 | Discussion on resource allocation for power saving | Zhejiang Lab |
| R1-2102811 | NR Sidelink Resource Allocation for UE Power Saving | Fraunhofer HHI, Fraunhofer IIS |
| R1-2102897 | Discussion on resource allocation for power saving | CMCC |
| R1-2102965 | Discussion on sidelink resource allocation enhancement for power saving | Xiaomi |
| R1-2103048 | Sidelink power saving solutions | Intel Corporation |
| R1-2103121 | Discussion on Sidelink Resource Allocation for Power Saving | Apple |
| R1-2103184 | Power Savings for Sidelink | Qualcomm Incorporated |
| R1-2103257 | On Resource Allocation for Power Saving | Samsung |
| R1-2103272 | Discussion on Sidelink Resource Allocation for Power Saving | Panasonic Corporation |
| R1-2103314 | Discussion on sidelink resource allocation for power saving | Sony |
| R1-2103331 | Discussion on resource allocation for power saving | ETRI |
| R1-2103378 | Discussion on resource allocation for power saving | LG Electronics |
| R1-2103416 | On Resource Allocation for Power Saving in NR Sidelink | Convida Wireless |
| R1-2103483 | Discussion on resource allocation for power saving | Sharp |
| R1-2103517 | Discussion on resource allocation for power saving | NEC |
| R1-2103537 | Sidelink resource allocation for power saving | InterDigital, Inc. |
| R1-2103548 | Sidelink resource allocation for power saving | Lenovo, Motorola Mobility |
| R1-2103592 | Discussion on sidelink resource allocation for power saving | NTT DOCOMO, INC. |
| R1-2103635 | Discussion on resource allocation for power saving | Hyundai Motors |
| R1-2103640 | Discussion on partial sensing and SL DRX impact | ASUSTeK |
| R1-2103663 | Resource allocation for power saving with partial sensing in NR sidelink enhancement | ITL |
| R1-2103704 | Resource allocation procedures for power saving | Ericsson |
| R1-2103710 | Discussion on resource allocation for power saving | ZTE, Sanechips |
| R1-2104090 | FL summary for AI 8.11.1.1 – resource allocation for power saving (1st check point) | Moderator (OPPO) |
| R1-2104091 | FL summary for AI 8.11.1.1 – resource allocation for power saving (2nd check point) | Moderator (OPPO) |
| R1-2104092 | FL summary for AI 8.11.1.1 – resource allocation for power saving (3rd check point) | Moderator (OPPO) |
| R1-2104093 | FL summary for AI 8.11.1.1 – resource allocation for power saving (final) | Moderator (OPPO) |
| R1-2104148 | Moderator summary of Email discussion/approval to reply LS in R1-2100021 | Moderator (ZTE) |
| 8.11.1.2 | Inter-UE coordination for Mode 2 enhancements | |
| R1-2102324 | Inter-UE coordination in sidelink resource allocation | Huawei, HiSilicon |
| R1-2102362 | Inter-UE coordination in mode 2 sidelink resource allocation | Nokia, Nokia Shanghai Bell |
| R1-2102412 | Inter-UE coordination in mode 2 of NR sidelink | OPPO |
| R1-2102468 | Discussion on inter-UE coordination in sidelink resource allocation | Spreadtrum Communications |
| R1-2102540 | Discussion on mode-2 enhancements | vivo |
| R1-2102576 | Considerations on mode 2 enhancements | CAICT |
| R1-2102607 | Discussion on inter-UE coordination in mode 2 enhancement | CATT, GOHIGH |
| R1-2102690 | Discussion on Mode 2 enhancements | MediaTek Inc. |
| R1-2102720 | Considerations on inter-UE coordination for mode 2 enhancements | Fujitsu |
| R1-2102781 | Discussion on techniques for inter-UE coordination | FUTUREWEI |
| R1-2102798 | Inter-UE coordination for mode 2 enhancements | Zhejiang Lab |
| R1-2102812 | Resource Allocation Enhancements for Mode 2 | Fraunhofer HHI, Fraunhofer IIS |
| R1-2102826 | Inter-UE coordination for enhanced resource allocation | Mitsubishi Electric RCE |
| R1-2102898 | Discussion on enhancements for mode-2 resource allocation | CMCC |
| R1-2102921 | Discussion on the inter-UE coordination | ZTE |
| R1-2102966 | Discussion on inter-UE coordination | Xiaomi |
| R1-2103049 | Inter-UE coordination solutions for sidelink resource allocation mode-2 | Intel Corporation |
| R1-2103122 | Discussion on Inter-UE Coordination | Apple |
| R1-2103185 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| R1-2103258 | On Inter-UE Coordination for Mode2 Enhancements | Samsung |
| R1-2103271 | Inter-UE coordination for mode 2 enhancement | ITL |
| R1-2103315 | Discussion on reliability and latency enhancements for mode 2 | Sony |
| R1-2103332 | Discussion on mode 2 enhancements | ETRI |
| R1-2103379 | Discussion on inter-UE coordination for Mode 2 enhancements | LG Electronics |
| R1-2103417 | On Inter-UE Coordination for Mode 2 Enhancements | Convida Wireless |
| R1-2103484 | Discussion on inter-UE coordination for Mode 2 enhancements | Sharp |
| R1-2103518 | Discussion on mode 2 enhancements | NEC |
| R1-2103538 | On Inter-UE coordination for Mode 2 enhancement | InterDigital, Inc. |
| R1-2103549 | Discussion on inter-UE coordination for Mode 2 enhancements | Lenovo, Motorola Mobility |
| R1-2103593 | Resource allocation for reliability and latency enhancements | NTT DOCOMO, INC. |
| R1-2103605 | Inter-UE coordination for Mode 2 enhancements | Panasonic Corporation |
| R1-2103636 | Discussion on mode 2 enhancements | Hyundai Motors |
| R1-2103648 | Discussion on V2X mode 2 enhancements | ASUSTeK |
| R1-2103705 | Mode 2 enhancements using Inter-UE coordination | Ericsson |
| R1-2104103 | Feature lead summary for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| 8.11.2 | Other | |
| R1-2102413 | Wake up signal for NR sidelink | OPPO |
| R1-2102541 | Other aspects on SL enhancements | vivo |
| R1-2102608 | Considerations on other aspects of NR mode2 enhancements | CATT, GOHIGH |
| R1-2102967 | Discssion on other design aspects for sidelink enhancement | Xiaomi |
| R1-2103123 | Network Assisted Resource Selection | Apple |
| R1-2103259 | On Sidelink Issues and RAN1 Impacts | Samsung |
| R1-2103392 | Physical layer impacts of sidelink DRX | Huawei, HiSilicon |
| R1-2103539 | On gNB-designated resources for inter-UE coordination | InterDigital, Inc. |
| R1-2103706 | Additional considerations for resource allocation procedures | Ericsson |
| R1-2103711 | Discussion on remaining issues for sidelink evaluation methodology | ZTE, Sanechips |
| 8.12 | NR Multicast and Broadcast Services | |
| R1-2102899 | Updated NR MBS work plan | CMCC |
| R1-2103985 | Session notes for 8.12 (NR Multicast and Broadcast Services) | Ad-Hoc Chair (Ericsson) |
| 8.12.1 | Mechanisms to support group scheduling for RRC_CONNECTED UEs | |
| R1-2102318 | Resource configuration and group scheduling for RRC_CONNECTED UEs | Huawei, HiSilicon |
| R1-2102414 | Group scheduling for NR Multicast and Broadcast Services | OPPO |
| R1-2102469 | Discussion on MBS group scheduling for RRC_CONNECTED UEs | Spreadtrum Communications |
| R1-2102501 | Discussion on Mechanisms to Support Group Scheduling for RRC_CONNECTED UEs | ZTE |
| R1-2102542 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | vivo |
| R1-2102609 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2102655 | Group Scheduling Mechanisms to Support 5G Multicast / Broadcast Services for RRC_CONNECTED Ues | Nokia, Nokia Shanghai Bell |
| R1-2102702 | Discussion on NR MBS group scheduling for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2102782 | Discussion on aspects for group scheduling | FUTUREWEI |
| R1-2102844 | Discussion on common frequency resource configuration for MBS | ETRI |
| R1-2102900 | Discussion on group scheduling mechanisms | CMCC |
| R1-2102909 | Summary#1 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2103050 | NR-MBS Group Scheduling for RRC_CONNECTED UEs | Intel Corporation |
| R1-2103124 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | Apple |
| R1-2103186 | Views on group scheduling for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2103260 | On mechanisms to support group scheduling for RRC_CONNECTED UEs | Samsung |
| R1-2103316 | Considerations on MBS group scheduling for RRC_CONNECTED UEs | Sony |
| R1-2103357 | Support of group scheduling for RRC_CONNECTED UEs | LG Electronics |
| R1-2103362 | Further discussion on group scheduling for RRC_CONNECTED UEs | Chengdu TD Tech, TD Tech |
| R1-2103419 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | Convida Wireless |
| R1-2103546 | Discussion on group scheduling mechanism for NR MBS | Lenovo, Motorola Mobility |
| R1-2103594 | Discussion on group scheduling mechanism for RRC_CONNECTED Ues | NTT DOCOMO, INC. |
| R1-2103658 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | ASUSTeK |
| R1-2103738 | Mechanisms to support MBS group scheduling for RRC_CONNECTED UEs | Ericsson |
| R1-2103831 | Summary#2 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2103877 | Summary#3 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2103901 | Summary#4 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2103923 | Summary#5 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2103961 | Summary#6 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2104013 | Summary#7 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2104044 | Summary#8 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2104045 | LS on G-RNTI and G-CS-RNTI for MBS | RAN1, CMCC |
| R1-2104080 | Summary#9 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2104097 | Summary#10 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| 8.12.2 | Mechanisms to improve reliability for RRC_CONNECTED UEs | |
| R1-2102319 | Mechanisms to improve reliability for RRC_CONNECTED UEs | Huawei, HiSilicon |
| R1-2102415 | UL feedback for RRC-CONNECTED UEs in MBS | OPPO |
| R1-2102470 | Mechanisms to improve reliability for RRC_CONNECTED UEs | Spreadtrum Communications |
| R1-2102502 | Discussion on Mechanisms to Improve Reliability for RRC_CONNECTED UEs | ZTE |
| R1-2102543 | Discussion on mechanisms to improve reliability for RRC_CONNECTED UEs | vivo |
| R1-2102552 | Discussion on MBS reliability for RRC_CONNECTED UEs | Google Inc. |
| R1-2102610 | Discussion on reliability improvement mechanism for RRC_CONNECTED UEs in MBS | CATT, CBN |
| R1-2102656 | Reliability Improvements for RRC_CONNECTED UEs | Nokia, Nokia Shanghai Bell |
| R1-2102703 | Discussion on mechanisms to improve reliability for RRC_CONNECTED Ues | MediaTek Inc. |
| R1-2102783 | Discussion on improving reliability for RRC_CONNECTED UEs | FUTUREWEI |
| R1-2102845 | Discussion on HARQ-ACK feedback method for MBS | ETRI |
| R1-2102875 | Reliability improvement for RRC_CONNECTED UEs in MBS | Potevio Company Limited |
| R1-2102901 | Discussion on reliability improvement | CMCC |
| R1-2103051 | Mechanisms to Improve Reliability of NR-MBS for RRC_CONNECTED UEs | Intel Corporation |
| R1-2103125 | Discussion on MBS reliability improvement for RRC_CONNECTED UEs | Apple |
| R1-2103187 | Views on UE feedback for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2103261 | On mechanisms to improve reliability for RRC_CONNECTED UEs | Samsung |
| R1-2103358 | Mechanisms to improve reliability of Broadcast/Multicast service | LG Electronics |
| R1-2103363 | Further discussion on reliability for RRC_CONNECTED UEs | Chengdu TD TECH, TD Tech |
| R1-2103420 | Discussion on reliability enhancement for RRC_CONNECTED UEs | Convida Wireless |
| R1-2103547 | Discussion on reliability improvement for RRC-CONNECTED UEs | Lenovo, Motorola Mobility |
| R1-2103595 | Discussion on HARQ-ACK feedback for multicast for RRC_CONNECTED Ues | NTT DOCOMO, INC. |
| R1-2103739 | Discussion on reliability mechanisms for NR MBS | Ericsson |
| R1-2103834 | FL summary#1 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2103900 | FL summary#2 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2103929 | FL summary#3 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2104031 | FL summary#4 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2104098 | FL summary#5 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| 8.12.3 | Basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs (Void-not be handled during this e-meeting) | |
| R1-2102553 | Discussion on MBS for RRC_IDLE/INACTIVE UE | Google Inc. |
| 8.12.4 | Other (Void-not be handled during this e-meeting) | |
| R1-2103364 | MBS related network planning for delivery mode 1 | Chengdu TD Tech, TD Tech |
| 8.13 | NR Dynamic spectrum sharing (DSS) | |
| R1-2103986 | Sesson notes for 8.13 (NR Dynamic spectrum sharing (DSS)) | Ad-hoc Chair (Samsung) |
| 8.13.1 | Cross-carrier scheduling (from Scell to Pcell) | |
| R1-2102309 | Discussion on SCell PDCCH scheduling P(S)Cell PDSCH or PUSCH | Huawei, HiSilicon |
| R1-2102416 | Discussion on cross-carrier scheduling from SCell to PCell | OPPO |
| R1-2102471 | Discussion on cross-carrier scheduling from SCell to Pcell | Spreadtrum Communications |
| R1-2102503 | Discussion on Cross-Carrier Scheduling from SCell to PCell | ZTE |
| R1-2102544 | Discussion on Scell scheduling Pcell | vivo |
| R1-2102611 | Discussion on cross-carrier scheduling from Scell to Pcell | CATT |
| R1-2102684 | On Cross-Carrier Scheduling from SCell to PCell/PSCell | MediaTek Inc. |
| R1-2102803 | Om cross-carrier scheduling from SCell to Pcell | Nokia, Nokia Shanghai Bell |
| R1-2102902 | Discussion on cross-carrier scheduling from SCell to Pcell | CMCC |
| R1-2102968 | Discussion on Cross-carrier scheduling from SCell to PCell | Xiaomi |
| R1-2103052 | On SCell scheduling PCell transmissions | Intel Corporation |
| R1-2103126 | Views on Rel-17 DSS SCell scheduling PCell | Apple |
| R1-2103188 | Cross-carrier scheduling from an SCell to the PCell/PSCell | Qualcomm Incorporated |
| R1-2103202 | Search space monitoring in sSCell and PCell | InterDigital, Inc. |
| R1-2103262 | Cross-carrier scheduling from SCell to PCell | Samsung |
| R1-2103333 | Cross-carrier scheduling from SCell to Pcell | ETRI |
| R1-2103359 | Discussion on cross-carrier scheduling from SCell to Pcell | LG Electronics |
| R1-2103596 | Discussion on cross-carrier scheduling enhancements for NR DSS | NTT DOCOMO, INC. |
| R1-2103609 | Cross-carrier scheduling (from Scell to Pcell) | Lenovo, Motorola Mobility |
| R1-2103645 | Enhanced cross-carrier scheduling for DSS | Ericsson |
| R1-2103659 | Discussion on cross-carrier scheduling from sSCell to PCell/PSCell | ASUSTeK |
| R1-2103846 | Summary of Email discussion [104b-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2103943 | Summary#2 of Email discussion [104b-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2104081 | Summary#3 of Email discussion [104b-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2104100 | Summary#4 of Email discussion [104b-e-NR-DSS-01] | Moderator (Ericsson) |
| 8.13.3 | Support efficient activation/de-activation mechanism for SCells in NR CA | |
| R1-2102310 | Discussion on efficient activation/de-activation mechanism for SCells | Huawei, HiSilicon |
| R1-2102417 | Discussion on efficient activation/de-activation for SCell | OPPO |
| R1-2102472 | Discussion on efficient activation/de-activation mechanism for SCells in NR CA | Spreadtrum Communications |
| R1-2102504 | Discussion on Support Efficient Activation De-activation Mechanism for SCells in NR CA | ZTE |
| R1-2102545 | Discussion on efficient activation/de-activation mechanism for Scells | vivo |
| R1-2102612 | Discussion on efficient activation and de-activation mechanism for SCell in NR CA | CATT |
| R1-2102685 | Discussion on temporary RS | MediaTek Inc. |
| R1-2102768 | Support efficient activation/de-activation mechanism for Scells | FUTUREWEI |
| R1-2102804 | On low latency Scell activation | Nokia, Nokia Shanghai Bell |
| R1-2102815 | Discussion on efficient activation mechanism for SCells | NEC |
| R1-2102903 | Discussion on efficient activation/de-activation mechanism for SCells | CMCC |
| R1-2103053 | On efficient activation/de-activation for SCells | Intel Corporation |
| R1-2103127 | On efficient SCell Activation/Deactivation | Apple |
| R1-2103189 | Efficient activation/de-activation mechanism for SCells in NR CA | Qualcomm Incorporated |
| R1-2103203 | Fast SCell Activation | InterDigital, Inc. |
| R1-2103263 | Reducing Latency for SCell Activation/Deactivation | Samsung |
| R1-2103597 | Discussion on efficient activation deactivation mechanism for Scells | NTT DOCOMO, INC. |
| R1-2103646 | Reduced Latency SCell Activation | Ericsson |
| R1-2103675 | Efficient activation/deactivation of SCell | ASUSTEK COMPUTER (SHANGHAI) |
| R1-2103885 | Summary#1 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2103886 | Summary#2 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2104109 | [Draft] Reply LS on temporary RS for efficient SCell activation in NR CA | Huawei |
| R1-2104110 | Reply LS on temporary RS for efficient SCell activation in NR CA | RAN1, Huawei |
| 8.14 | Study on XR Evaluations for NR (RAN1) | |
| R1-2103190 | Updated Work Plan for Rel-17 SI on XR Evaluations for NR | Qualcomm Incorporated |
| R1-2103191 | Updated TR for Study on XR Evaluation | Qualcomm Incorporated |
| R1-2103988 | Session notes for 8.14 (Study on XR Evaluations for NR) | Ad-Hoc Chair (Ericsson) |
| R1-2104117 | LS response on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) | RAN1, Qualcomm Incorporated |
| 8.14.1 | Traffic Model | |
| R1-2102320 | Traffic model for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2102418 | Discussion on the XR traffic models for evaluation | OPPO |
| R1-2102546 | Discussion on traffic models of XR | vivo |
| R1-2102616 | XR traffic model | CATT |
| R1-2102686 | Traffic Model for XR and CG | MediaTek Inc. |
| R1-2102769 | XR traffic model | FUTUREWEI |
| R1-2102827 | On Traffic Model for XR study | Nokia, Nokia Shanghai Bell |
| R1-2102955 | Traffic model for XR | Ericsson |
| R1-2102969 | Discussion on Traffic Model for XR services | Xiaomi |
| R1-2103054 | Traffic Model for XR | Intel Corporation |
| R1-2103128 | Views on XR traffic model | Apple |
| R1-2103192 | Remaining Issues on XR Traffic Models | Qualcomm Incorporated |
| R1-2103264 | Traffic model for XR | Samsung |
| R1-2103278 | Further Discussion on Traffic Model for XR Evaluations | ZTE, Sanechips |
| R1-2103317 | Considerations on XR traffic model | Sony |
| R1-2103360 | Discussion on traffic models for XR evaluation | LG Electronics |
| R1-2103429 | UL traffic flows for XR applications | InterDigital, Inc. |
| R1-2103437 | XR Traffic Model Considerations | AT&T |
| R1-2103598 | Discussion on traffic model for XR | NTT DOCOMO, INC. |
| R1-2104116 | FL Summary of 104bis-e agreements and email discussions on XR traffic models | Moderator (Qualcomm) |
| 8.14.2 | Evaluation Methodology | |
| R1-2102321 | Evaluation methodology for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2102419 | Discussion on the XR evaluation methodology | OPPO |
| R1-2102547 | Discussion on evaluation methodologies of XR | vivo |
| R1-2102613 | Evaluation methodology and performance index for XR | CATT |
| R1-2102687 | On Evaluation Methodology for XR and CG | MediaTek Inc. |
| R1-2102770 | XR evaluation methodology | FUTUREWEI |
| R1-2102828 | Development of the Evaluation Methodology for XR Study | Nokia, Nokia Shanghai Bell |
| R1-2102956 | Evaluation methodology for XR | Ericsson |
| R1-2102970 | Discussion on evaluation methodology for XR services | Xiaomi |
| R1-2103055 | Evaluation Methodology | Intel Corporation |
| R1-2103129 | Views on XR evaluatoin methodology | Apple |
| R1-2103193 | Remaining Issues on Evaluation Methodology for XR | Qualcomm Incorporated |
| R1-2103265 | Evaluation methodology and KPIs for XR | Samsung |
| R1-2103279 | On XR Evaluation Methodology | ZTE, Sanechips |
| R1-2103361 | Discussion on evaluation methodologies for XR | LG Electronics |
| R1-2103430 | Remaining Issues on XR Evaluations and KPIs | InterDigital, Inc. |
| R1-2103438 | XR Evaluation Assumptions | AT&T |
| R1-2103599 | Discussion on evaluation methodology for XR | NTT DOCOMO, INC. |
| R1-2103827 | Summary of email discussion for evaluation methodology and assumptions | Moderator (vivo) |
| R1-2104127 | Summary of [104b-e-NR-XR-02] Email discussion on evaluation methodology | Moderator (vivo) |
| R1-2104128 | Draft template for XR evaluation results | Moderator (vivo) |
| 8.14.3 | Initial Performance Evaluation Results | |
| R1-2102322 | Initial evaluation results for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2102420 | Initial performance results for XR evaluation | OPPO |
| R1-2102548 | Initial performance evaluation results of XR | vivo |
| R1-2102614 | Evaluation results of XR performance | CATT |
| R1-2102707 | 8.14.3 Initial Performance and Evaluation Results for XR and CG | MediaTek Inc. |
| R1-2102771 | XR initial evaluations | FUTUREWEI |
| R1-2102829 | Performance results in indoor hotspot and dense urban deployments of CG and VR/AR applications | Nokia, Nokia Shanghai Bell |
| R1-2102904 | Initial XR Evaluation Results | CMCC |
| R1-2102957 | Initial XR performance evaluation results | Ericsson |
| R1-2103130 | Initial performance evaluation on XR | Apple |
| R1-2103194 | Initial Evaluation Results for XR Capacity and UE Power Consumption | Qualcomm Incorporated |
| R1-2103280 | Initial Performance Evaluation Results for XR | ZTE, Sanechips |
| R1-2103431 | Performance Evaluation Results on XR applications | InterDigital, Inc. |
| R1-2103439 | XR Initial Performance Results | AT&T |
| R1-2103833 | Initial performance evaluation on XR | Apple |
| R1-2103888 | Initial performance evaluation on XR | Apple |
| R1-2104118 | FL Summary of initial evaluation results for XR over NR | Moderator (Qualcomm) |
| 8.14.4 | Other | |
| R1-2102421 | Discussion on the support of XR/CG service in sidelink-unlicensed | OPPO |
| R1-2102549 | Challenges and potential enhancements of XR | vivo |
| R1-2102615 | Potential area of NR enhancement for the support of XR services | CATT |
| R1-2102830 | Potential enhancements for better XR support over NR | Nokia, Nokia Shanghai Bell |
| R1-2102958 | Mobility and XR applications | Ericsson |
| R1-2102971 | Discussion on potential enhancement for supporting XR | Xiaomi |
| R1-2103131 | Views on potential enhancements for XR | Apple |
| R1-2103195 | Potential Enhancements for XR | Qualcomm Incorporated |
| R1-2103281 | Considerations on XR Specific Enhancement | ZTE, Sanechips |
| R1-2103390 | Challenges and potential enhancements for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2103432 | Potential enhancements for supporting XR | InterDigital, Inc. |
| 8.15 | Study on NB-IoT/eMTC support for Non-Terrestrial Network | |
| R1-2102753 | FS_LTE_NBIOT_eMTC_NTN work plan | MediaTek Inc. |
| R1-2103897 | Text proposal for TR 36.763 for RAN1#104bis-e Agreements | Moderator (MediaTek) |
| R1-2103987 | Session notes for 8.15 (Study on NB-IoT/eMTC support for Non-Terrestrial Network) | Ad-Hoc Chair (Ericsson) |
| R1-2104146 | Study on Narrow-Band Internet of Things (NB-IoT) / enhanced Machine Type Communication (eMTC) support for Non-Terrestrial Networks (NTN) (Release 17) | Rapporteur (MediaTek) |
| R1-2104147 | Link budget result calibration Spreadsheet for IoT NTN | Rapporteur (MediaTek) |
| 8.15.1 | Scenarios applicable to NB-IoT/eMTC | |
| R1-2102343 | Application scenarios of IoT in NTN | Huawei, HiSilicon |
| R1-2102422 | Discussion on scenarios applicable to NB-IoT/eMTC | OPPO |
| R1-2102550 | Discussion on scenarios applicable to NB-IoT_eMTC for NTN | vivo |
| R1-2102617 | Applicable scenario and initial evaluation result to NB-IoT/eMTC | CATT |
| R1-2102750 | Discussion on NTN-IoT scenario with MEO | Hughes/EchoStar |
| R1-2102754 | Scenarios applicable to IoT NTN | MediaTek Inc. |
| R1-2102831 | Link budget evaluations for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2102905 | Discussion on scenarios applicable to NB-IoT/eMTC | CMCC |
| R1-2102916 | Discussion on the scenarios and assumption for IoT-NTN | ZTE |
| R1-2102972 | Discussion on the link budget of NBIoT and eMTC over NTN | Xiaomi |
| R1-2103060 | On scenarios and evaluations for NB-IoT and eMTC based NTN | Ericsson |
| R1-2103070 | Scenarios applicable to NB-IoT/eMTC | Qualcomm Incorporated |
| R1-2103132 | Link Budget Analysis of IoT NTN | Apple |
| R1-2103266 | Initial link budget evaluation for NB-IoT/eMTC | Samsung |
| R1-2103318 | Scenarios for IoT-NTN | Sony |
| R1-2103716 | Link budget analysis for Set-4 | Sateliot, Gatehouse, Thales |
| R1-2103826 | Summary#1 of AI 8.15.1 Scenarios applicable to NB-IoT/eMTC | Moderator (MediaTek) |
| R1-2103907 | Summary#2 of AI 8.15.1 Scenarios applicable to NB-IoT/eMTC | Moderator (MediaTek) |
| R1-2103962 | Summary#3 of AI 8.15.1 Scenarios applicable to NB-IoT/eMTC | Moderator (MediaTek) |
| 8.15.2 | Enhancements to time and frequency synchronization | |
| R1-2102344 | Discussion on time and frequency synchronization enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2102423 | Discussion on enhancements to time and frequency synchronization | OPPO |
| R1-2102473 | Consideration on enhancements to time and frequency synchronization | Spreadtrum Communications |
| R1-2102618 | Time and frequency synchronization for NB-IoT/eMTC | CATT |
| R1-2102736 | Time and frequency synchronization to NB-IoT in NTN | Asia Pacific Telecom, FGI, ITRI, III |
| R1-2102755 | Enhancements to time and frequency synchronization for IoT NTN | MediaTek Inc. |
| R1-2102758 | Summary #1 of AI 8.15.2 Enhancements to time and frequency synchronization | MediaTek Inc. |
| R1-2102832 | Enhancement to time and frequency synchronization for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2102906 | Enhancements to time and frequency synchronization for IoT NTN | CMCC |
| R1-2102917 | Discussion on the synchronization for IoT-NTN | ZTE |
| R1-2102973 | Discussion on time and frequency synchronization for IoT NTN | Xiaomi |
| R1-2103056 | On synchronization for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2103061 | On time and frequency synchronization enhancements for IoT NTN | Ericsson |
| R1-2103071 | Enhancements to time and frequency synchronization | Qualcomm Incorporated |
| R1-2103133 | On Time and Frequency Synchronization in IoT NTN | Apple |
| R1-2103267 | On enhancements to time and frequency synchronization | Samsung |
| R1-2103273 | Time/Frequency Synchronization for IoT NTN | InterDigital, Inc. |
| R1-2103319 | Time and frequency synchronisation enhancements for IoT-NTN | Sony |
| R1-2103528 | Time and frequency synchronization for IoT NTN | Lenovo, Motorola Mobility |
| R1-2103908 | Summary#2 of AI 8.15.2 Enhancements to time and frequency synchronization | Moderator (MediaTek) |
| R1-2103950 | Summary#3 of AI 8.15.2 Enhancements to time and frequency synchronization | Moderator (MediaTek) |
| R1-2103964 | Summary#4 of AI 8.15.2 Enhancements to time and frequency synchronization | Moderator (MediaTek) |
| 8.15.3 | Timing relationship enhancements | |
| R1-2102345 | Discussion on timing relationship enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2102424 | Discussion on timing relationship enhancements | OPPO |
| R1-2102474 | Consideration on timing relationship enhancements | Spreadtrum Communications |
| R1-2102619 | Timing relationship enhancement for NB-IoT/eMTC | CATT |
| R1-2102737 | Timing relationship enhancements to NB-IoT in NTN | Asia Pacific Telecom, FGI, ITRI, III |
| R1-2102756 | Timing relationship enhancements for IoT NTN | MediaTek Inc. |
| R1-2102800 | Timing relationship enhancements to support NB-IoT eMTC in Non-Terrestrial Network | Zhejiang Lab |
| R1-2102833 | Timing relationship enhancements for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2102907 | Timing relationship enhancements for IoT NTN | CMCC |
| R1-2102918 | Discussion on timing relationship for IoT-NTN | ZTE |
| R1-2102974 | Discussion on the timing relationship enhancement for IoT NTN | Xiaomi |
| R1-2103057 | On timing relationship for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2103062 | On timing relationship enhancements for IoT NTN | Ericsson |
| R1-2103072 | Timing relationship enhancements | Qualcomm Incorporated |
| R1-2103134 | On Timing Relationship Enhancement in IoT NTN | Apple |
| R1-2103268 | Timing relationship enhancements | Samsung |
| R1-2103274 | Timing relationship enhancement for IoT NTN | InterDigital, Inc. |
| R1-2103320 | Timing relationships for IoT-NTN | Sony |
| R1-2103529 | Timing relationship enhancements for IoT NTN | Lenovo, Motorola Mobility |
| R1-2103847 | FL summary #1 of AI 8.15.3 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2103887 | FL summary #2 of AI 8.15.3 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2103957 | FL summary #3 of AI 8.15.3 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2104083 | FL summary #4 of AI 8.15.3 Timing relationship for IoT-NTN | Moderator (Sony) |
| 8.15.4 | Enhancements on HARQ | |
| R1-2102346 | Discussion on HARQ enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2102425 | Discussion on HARQ enhancements | OPPO |
| R1-2102475 | Consideration on enhancements on HARQ | Spreadtrum Communications |
| R1-2102551 | Discussion on HARQ enhancements on NB-IoT/eMTC for NTN | vivo |
| R1-2102620 | HARQ operation enhancement for NB-IoT/eMTC | CATT |
| R1-2102738 | Enhancements on HARQ to NB-IoT in NTN | Asia Pacific Telecom, FGI, ITRI, III |
| R1-2102757 | Enhancements on HARQ for IoT NTN | MediaTek Inc. |
| R1-2102834 | HARQ for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2102908 | Enhancements on HARQ for IoT NTN | CMCC |
| R1-2102919 | Discussion on HARQ for IoT-NTN | ZTE |
| R1-2102975 | Discussion on the HARQ enhancement for IoT NTN | Xiaomi |
| R1-2103063 | On HARQ enhancements for IoT NTN | Ericsson |
| R1-2103073 | Enhancements on HARQ | Qualcomm Incorporated |
| R1-2103135 | On HARQ Enhancement in IoT NTN | Apple |
| R1-2103269 | On enhancements on HARQ | Samsung |
| R1-2103275 | HARQ enhancement for IoT NTN | InterDigital, Inc. |
| R1-2103321 | HARQ issues for IoT-NTN | Sony |
| R1-2103530 | HARQ enhancement for IoT NTN | Lenovo, Motorola Mobility |
| R1-2103803 | Summary#1 of enhancements on HARQ | Moderator(Samsung) |
| R1-2103804 | Summary#2 of enhancements on HARQ | Moderator(Samsung) |
| R1-2103805 | Summary#3 of enhancements on HARQ | Moderator(Samsung) |
| R1-2103806 | Summary#4 of enhancements on HARQ | Moderator(Samsung) |
| 8.15.5 | Other | |
| R1-2102426 | Discussion on other aspects | OPPO |
| R1-2102476 | Consideration on other design aspects for IOT NTN | Spreadtrum Communications |
| R1-2102835 | Applicability of NB-IoT/eMTC features for NTN | Nokia, Nokia Shanghai Bell |
| R1-2102920 | Discussion on additional enhancement for IoT-NTN | ZTE |
| R1-2102976 | Discussion on the other design aspects for IoT NTN | Xiaomi |
| R1-2103064 | On evaluation assumptions for NB-IoT and eMTC based NTN | Ericsson |
| R1-2103074 | Other aspects for NTN IOT | Qualcomm Incorporated |
| R1-2103396 | Other aspects to support IoT in NTN | Huawei, HiSilicon |
| 8.16 | Other | |
| R1-2102671 | Discussion on issues of NR codeword mapping | ZTE |
| R1-2103196 | Rel-17 TEI Topics | Qualcomm Incorporated |
| R1-2103604 | Summary on Rel-17 TEI related discussion | Moderator (NTT DOCOMO INC.) |
| R1-2103703 | TEI-17 proposal targeting the false PMI reporting issue | Ericsson, NTT DOCOMO, Inc., Softbank, Verizon, T-Mobile USA |
| R1-2103740 | NR positioning support for TA-based positioning in E-CID (TEI) | Ericsson, Polaris Wireless, Verizon, Intel, NTT Docomo, China Telecom, FirstNet, Deutsche Telekom |
| R1-2103741 | Introduction of type 2 Timing Advance measurement | Ericsson, Polaris Wireless, Verizon, Intel, NTT Docomo, China Telecom, FirstNet, Deutsche Telekom |
| R1-2103745 | Enhancements on the scheduling of PUSCH over multiple slots | Huawei, HiSilicon |
| R1-2103816 | Summary on [104b-e-NR-R17-TEI-01] | Moderator (NTT DOCOMO, INC.) |